Disc update (iDSK, cpctelera)

[cperezgrin]

Hi, how are your cpcretrodev projects going? Mine is almost done, but there's some strange behaviour I wonder if it is possible to fix. I want to rename the main bin created by cpctelera to let know the user that "loader.bas" is the file he needs to run the game. So I execute the following commands after the build (where cobra.bin is the file to rename to data0.bin)

../cpctelera/tools/iDSK-0.13/bin/iDSK.exe cobra.dsk -g cobra.bin
../cpctelera/tools/iDSK-0.13/bin/iDSK.exe cobra.dsk -r cobra.bin
mv cobra.bin data0.bin
../cpctelera/tools/iDSK-0.13/bin/iDSK.exe cobra.dsk -i data0.bin

Everything works fine, data0.bin is included in the dsk and the loader.bas can run it without problem. But the strange thing happens when I type CAT to the disk, because it still lists cobra.bin. Although it says "not found" when I try to load it. It seems like the file directory is not updated after the remove and include.

Winamp disc editor doen't show the file.

DSK : cobra.dsk
Mode : export fichier Amsdos
Fichier Amsdos : cobra.bin

------------------------------------
DSK : cobra.dsk
Mode : Effacement fichier dans la DSK
Fichier Amsdos : cobra.bin
SCREEN1 .BIN : 17 Ko
SCREEN0 .BIN : 17 Ko
DATA1   .BIN : 6 Ko
SCREEN2 .BIN : 17 Ko
DATA2   .BIN : 6 Ko
LOADER  .BAS : 1 Ko
------------------------------------
DSK : cobra.dsk
Mode : Import fichier dans Dsk
Fichier Amsdos : data0.bin
Le fichier a d▒j▒ une en-t▒te
DATA0   .BIN : 42 Ko
SCREEN1 .BIN : 17 Ko
SCREEN0 .BIN : 17 Ko
DATA1   .BIN : 6 Ko
SCREEN2 .BIN : 17 Ko
DATA2   .BIN : 6 Ko
LOADER  .BAS : 27 Ko
------------------------------------

Do I need to do something else to update the directory?

[teopl]

Hi, well my project would never be finished if there was no deadline, I keep adding and breaking stuff 

So, looks like your problem is not very big, you just want to indicate what needs to be loaded/started...

I did not use iDSK for removing, I only used it for adding files and winape auto starts my game, this is how I solved it:

[teopl]

Sorry I messed up the post...



upload photo image

So, there are also other tools like ManageDsk and CPCDiskXP which have command line interface.
You can try to extract the files and add them to *new* DSK created.

[cperezgrin]

Yes, I finally build the dsk file by myself from a new one.

[pelrun]

I've never had any luck with getting iDSK to modify an existing image; it's always corrupted them. I ended up just rebuilding the image from scratch every time like you did.

[ronaldo]

So I execute the following commands after the build (where cobra.bin is the file to rename to data0.bin)

../cpctelera/tools/iDSK-0.13/bin/iDSK.exe cobra.dsk -g cobra.bin
../cpctelera/tools/iDSK-0.13/bin/iDSK.exe cobra.dsk -r cobra.bin
mv cobra.bin data0.bin
../cpctelera/tools/iDSK-0.13/bin/iDSK.exe cobra.dsk -i data0.bin

Hi @cperezgrin,

There is one thing I don't understand. Is there any particular reason to do this manually after the build? Why not to change build_config.mk to make CPCtelera generate data0.bin instead of cobra.bin?

As others point out, iDSK is not particularly reliable. For CPCtelera 2.0, we will probably change to use dskgen from Augusto Ruiz. At the moment, it works fine if you limit yourself to add files.

[LTronic]

Hi @cperezgrin,

There is one thing I don't understand. Is there any particular reason to do this manually after the build? Why not to change build_config.mk to make CPCtelera generate data0.bin instead of cobra.bin?

As others point out, iDSK is not particularly reliable. For CPCtelera 2.0, we will probably change to use dskgen from Augusto Ruiz. At the moment, it works fine if you limit yourself to add files.

If using cpctelera 1.5 (dev branch) iDSK 0.19 works for me 100% reliable. I made a pull request for this, feel free to have a look.

[cperezgrin]

I didn't know I can change the bin filename in the config file . I'm always do things the hard way

[ronaldo]

If using cpctelera 1.5 (dev branch) iDSK 0.19 works for me 100% reliable. I made a pull request for this, feel free to have a look.

I know you did, and I appreciate your work. However, doing such a change in CPCtelera is not trivial. "It works for me" is not valid to change something that might broke builds for many developers. It requires a lot of time to be deeply tested before changing it.


At the present moment I don't have the time required to perform the tests, so it is on stand by. In any case, as I already pointed out, we may finally discard it if we change to dskgen, which is much more solid and has much more functionality than iDSK. There is no point in having many ways to create DSK unless they provided very different functionalities. In this case, dskgen does everything iDSK does and much more.


Whichever the final decision, thank you for your effort and collaboration . We consider every collaboration even if some of them are finally discarded. Many of our own developments have also been discarded in the end.

[LTronic]

I know you did, and I appreciate your work. However, doing such a change in CPCtelera is not trivial. "It works for me" is not valid to change something that might broke builds for many developers. It requires a lot of time to be deeply tested before changing it.


At the present moment I don't have the time required to perform the tests, so it is on stand by. In any case, as I already pointed out, we may finally discard it if we change to dskgen, which is much more solid and has much more functionality than iDSK. There is no point in having many ways to create DSK unless they provided very different functionalities. In this case, dskgen does everything iDSK does and much more.


Whichever the final decision, thank you for your effort and collaboration . We consider every collaboration even if some of them are finally discarded. Many of our own developments have also been discarded in the end.

No problem, I was not aware of dskgen if it's the better tool then it's worth the switch
I was basically stuck in my project because of the iDSK weirdness, so I had to move on in one way or another

[gryken]

Hello,
Under linux, is iDSK the only tools to handle DSK ?
After, some tests, it seems that iDSK doesn't handle ESDK ?
Do you know others tools to handle DSK and ESDK, in order to replace iDSK ?
( callable from cpctelera ?)
Thanks