static-void / cpcsdk

Automatically exported from code.google.com/p/cpcsdk
0 stars 0 forks source link

IDSK can modify files when putting them in the dsk #61

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Launch iDSK <dsk> -i <file>

What is the expected output? 
The file in the dsk must be the same than the file on the pc (modulo the header)

What do you see instead?
The files may have been corrupted.

On what operating system?
Linux

Please provide any additional information below.
cpcfs seems better ;)

Original issue reported on code.google.com by giot.romain on 15 Jul 2011 at 4:23

GoogleCodeExporter commented 8 years ago
I've seen cpcfs erase other files on the dsk, so be careful with it.
Can you provide more info ? Something like this would help :

xxd file1.bin > file1.hex
xxd file2.bin > file2.hex

diff file?.hex

Original comment by pulkoma...@gmail.com on 15 Jul 2011 at 5:22

GoogleCodeExporter commented 8 years ago
Sadly I cannot send you the files. It is secret project and the file contains 
to many interesting things;)

Here are the expected values (xxd):

0000250: 2901 6203 ed43 0501 2605 2211 01ed 7bc3  ).b..C..&."...{.
0000260: 02c9 0000 0000 0000 0000 0000 0000 0000  ................
0000270: 0000 0000 0000 0000 18cd 0000 0000 0000  ................
...

Here are the obtained values (hexdump -C):
00000250  29 01 62 03 ed 43 05 01  26 05 22 11 01 ed 7b c3  |).b..C..&."...{.|
00000260  10 c5 bc 4e ff 7f 00 00  c0 cc bc 4e ff 7f 00 00  |...N.......N....|
00000270  90 c8 bc 4e ff 7f 00 00  ce 58 40 00 00 00 00 00  |...N.....X@.....|
...

I think the rest of the file is wrong

Original comment by giot.romain on 15 Jul 2011 at 6:54

GoogleCodeExporter commented 8 years ago
Hello, is it the same bug as mentioned on 
http://www.cpcwiki.eu/forum/programming/idsk-clobbers-existing-file/msg91611/ ?

Original comment by stephane...@gmail.com on 27 Dec 2014 at 10:54