From: David H. <DHe...@is...> - 2003-09-23 08:16:37
|
Argh, the thing got posted pre-maturely > Hi all, >=20 > In the concept version of the release notes, I didn't mention the=20 > DirAsDsk feature. Should it be included? > In other words: is it mature enough to be a 'supported' feature? =20 Include it in the release notes, but mention the following: -The directory may not contain subdirectories (no MSX-DOS2 is=20 not yet supported) -The total size of the files must fit on a regular 720 KB=20 disk (didn't check enough to see what happens if there is to =20 much data) So it works for most regular uses of the feature. I'm also wondering what happens with the 'hidden' files I use to write = the bootsector and sectorcaches ? I suppose they simply show up under = Win32 =20 =20 > What happens on Win32 if a user does: > openmsx -diska a: > with a real MSX floppy with, possibly, some sector based data? > I'm afraid that the disk can be damaged. Please let me know. :-) some reactions: 1) sector based data: the DirAsDsk feature only read's files,=20 not sectors, so pure sector data is ignored. The code uses the OS'es = file routines, so I even doubt if Win32 can read single sided DD disks 2) Shouldn't '-diska a:' be intercepted as a special case in the Win32 = version, to open it as a 720KB file. I once read that each version of = Windows(tm) as seperate routines for that kind of stuff but then again = I'm no Win32 developer. 3) I don't run openMSX under Win32, so I leave testing to someone else = ;) rgds, David Heremans |