-[diskmanipulator create testhd.dsk 30M 30M]
- this gives disk I/O error in basic (not a DOS disk
in DOS); so partition table is invalid? Using
only one partition argument works.
- On a fresh (single partition) harddisk image (openmsx
-ext ide -hda testhd.dsk):
- copy MSX-DOS2 to it
- in DOS2, do mkdir mbwave
- on host OS: download MBWAV116.LZH, unLZH it to
/tmp/MBWAV
- start openMSX with the hd image and type in the
console:
diskmanipulator chdir hda mbwave
diskmanipulator import hda /tmp/MBWAV
- in DOS2, type:
cd mbwave
mbwave
- RESULT: Bad File Allocation Table reading drive A:
(Aborted)
- NOTE: when the files from MBWAV116.LZH are copied
manually (in DOS, from a floppy disk image)
everything works fine
- <wouter_> I tried this:
create an empty disk image (720kb)
import a small file
import a big file (several megabytes)
--> first file is corrupted
Conclusion: there are some serious issues in the
diskmanipulator!
Logged In: YES
user_id=78178
Originator: YES
The import problems are fixed now, it seems. (Thanks Wouter, revision 6114.) At least they don't occur anymore in the above mentioned scenarios.
Logged In: YES
user_id=78178
Originator: YES
Wouter also fixed the create issue, but a remaining problem is what BiFi experienced (on Windows): in some endless loop openMSX keeps creating a bigger and bigger disk image file.
<BiFiMSX> a single partition works
<wouter_> any size?
<BiFiMSX> single 30MB
<wouter_> ok, good enough
<BiFiMSX> I tried a 30M 720K but that did an infinite loop
<wouter_> and what exactly happens for multiple partitions? it keeps on writing to your HD?
<BiFiMSX> yes
<BiFiMSX> that 30M 720K attempt is 370MB when I killed openMSX
Logged In: YES
user_id=78178
Originator: YES
endless loop was also fixed in revision 6119 by wouter (bug in Windows version of truncate() method).
There are no known remaining problems.