Page 2 of 2
Re: OSDK 1.5
Posted: Tue Feb 24, 2015 7:51 pm
by Dbug
Indeed the -o0 and -o1 descriptions are inverted.
I guess I will invert the descriptions so the behavior does not change, which means that -o0 is the mode with the BASIC loader that switches to HIRES before loading the rest, while -o1 is the mode that simply has a tape header that loads directly to 0xa000.
I will make sure this is fixed in the next release.
For Tap2Dsk, I will wait until somebody that uses the tool modifies it and test the result
I guess the next version will also have sample code to show how to replay MYM musics - I will add to the OSDK some test musics, the ones I used in my earlier demos so we have no right issue -.
Re: OSDK 1.5
Posted: Wed Mar 18, 2015 11:34 pm
by Chema
Guys, I'm sorry. I just ran tap2dsk with no options to see the usage and the -i for the INIST and others are there, so it is the correct version. However building it with OSDK 1.5 does not create a disk with the INIST as it did on the last version.
I, however, get some kind of what seem to be debugging messages from the tool:
Code: Select all
Reading build\stest.tap
Found STEST
Storing STEST.COM
Old -> MFM v1.2
read old.
writing header...
writing size 0 track 0 sector 0...
writing size 0 track 0 sector 1...
writing size 0 track 0 sector 2...
writing size 0 track 0 sector 3...
...
writing size 0 track 20 sector 16...
done.
I wonder if my attempt to use the -i and/or -n options (disk name is not set either) is being wrongly interpreted as a kind of verbose option or something...
Re: OSDK 1.5
Posted: Thu Mar 19, 2015 1:40 am
by iss
Hi Chema,
tap2dsk+old2mfm from OSDK 1.5 are working for me fine. This is under Linux.
I'm using command line:
tap2dsk -n'MONITOR' -i'!QUIT:!MONITOR' Monitor.tap Monitor.dsk
old2mfm Monitor.dsk
and the generated DSK works. if I change to ... -nMONITOR ... i.e. without quotes - DSK is bad.
You can check your .bat files and try to add quotes.
Additionally, there should be no space after the options (-n,-i).
I hope this helps.
Re: OSDK 1.5
Posted: Thu Mar 19, 2015 2:27 pm
by Chema
Mmmm... I think all that should be correct.
But maybe there is even a simpler reason... Maybe I modified some .bat file to support the options in the build process using labels.
Damn, I simply cannot remember. Will check and report.
Still the "writing..." messages are a bit annoying....
Re: OSDK 1.5
Posted: Thu Mar 19, 2015 2:55 pm
by Dbug
What about adding a -v (verbose on/off) option?
Re: OSDK 1.5
Posted: Thu Mar 19, 2015 4:07 pm
by iss
The "writing" messages come from 'old2mfm'.
And here is why they are annoying:
Code: Select all
for(s=0;s<sides;s++)
for(t=0;t<tracks;t++) {
for(i=0;i<sectors;i++) {
printf("writing size %d track %d sector %d...\n", s, t, i);
Obvious 'size' should be 'side'
.
And looking sources there is no option '-v' for both 'tap2dsk' and 'old2mfm'.
Re: OSDK 1.5
Posted: Thu Apr 02, 2015 4:24 pm
by Chema
I found what was wrong... in the bin directory the make.bat script contains:
Code: Select all
::
:: Generate the DSK file. If OSDKFILE is empty we assume (hm hmmm) that the caller is packaging itself with floppybuilder. (WIP)
::
IF "%OSDKDISK%"=="" GOTO EndBuildDisk
IF "%OSDKFILE%"=="" GOTO EndBuildDisk
::%OSDK%\bin\DskTool.exe -n%OSDKDNAME% -i%OSDKINIST% %OSDKDISK% build\%OSDKNAME%.tap build\%OSDKNAME%.dsk
%OSDK%\bin\tap2dsk.exe %OSDKDISK% build\%OSDKNAME%.tap build\%OSDKNAME%.dsk
%OSDK%\bin\old2mfm.exe build\%OSDKNAME%.DSK
As you can see when using tap2dsk the -n and -i options are not used. Adding them this way:
Code: Select all
%OSDK%\bin\tap2dsk.exe -n%OSDKDNAME% -i%OSDKINIST% %OSDKDISK% build\%OSDKNAME%.tap build\%OSDKNAME%.dsk
did the trick.
Still the messages generated by the old2mfm are a bit annoying... I don't remember they were there, but it would be nice if they are removed... Please?
Re: OSDK 1.5
Posted: Thu Apr 02, 2015 4:39 pm
by Dbug
I added the two issues to the issue tracker:
http://osdk.defence-force.org/index?page=issues
I should probably add some documentation pages for Old2Mfm and Tap2Dsk, and I was thinking that possibly I should just remove WriteDsk from the OSDK, most people don't need it, and the ones who need it probably don't have a combination of OS and hardware where it would actually work.
Re: OSDK 1.5
Posted: Thu Apr 02, 2015 5:29 pm
by Chema
Thanks!
I agree with you about writedsk.
Keeping OSDK as clean as possible is a good idea, imho.