you 2 guys are just plain stupid!

we know


(got it working now using 'disk manager', some ancient tool to make MSX images I guess)

RO: Neveremind, never saw you were using that DiskManager too

Sorry, but I'ma have to agree with Ro here. You guys *ARE* err... Not too bright. Okay, here's how it works...

1) Get NLMSX 0.48 (You prolly have it)
2) Get the Diskmanager the guy from RuMSX made, it's hip...
3) Make a new disk like Ro said, dump your files on it.
4) SAVE the changes you made to the disk.
5) CLOSE the disk manager (Or at least make SURE you closed the file)

And that's it, always has worked, always will work... If this does not work for you, you must have the special BillGatesReallyHatesYou Windows version that doesn't allow you to make .dsk images. If that is the case, tell me where to download the files and where to mail de .dsk image and I'll mail it to you. (I'll even test it first.)

Good luck,

Tobes

P.S. Don't be stubborn, try again and follow ALL the steps.

Yeah yeah, Latok and I used a WRONG disk manager, as posted BEFORE, so who's plain stupid here?
Using DskExplorer will result in files being visible on disk but they'll be empty when you try to load them (as also said before), a sector view will result you seeing all data of the files IS stored on disk, but somehow, NlMSX chokes in it...

Though I've got that DskExplorer 0.84 working ONCE!

PS. And of course we close the .dsk-files before checking 'em in NlMSX (0.48)


Edit: DskManager changed to DskExplorer

Indeed, d-fader. And if you guys look at the threadtitle, which is 'What's up with these 'DSK-managers'', you MIGHT come to the conclusion that we ARE talking about the DSK-managers here and not about the IQ-level of d-fader and me. You can trust us, we may be a bunch of retarded plants, but we know something about MSX and there really IS more going on than just 'you two don't know how to create DSK-images, you are stupid'...

Please, read the thread a bit better before you give misplaced personal opinions. It only makes yourself look stupid. And YES, Ro. I know you were just kidding Sonic his reply had a bit more serious intonation, though

I wonder if these problems only occur while using DskExplorer 0.84 or also when using that other one called Diskmanager. That one is created by the same dude who developed RuMSX, right?

Frankly, I use the all-purpose image manager 'WinImage', which is not free, but it does work. It would be great to have a DSKmanagers with the capabilities of WinImage, but with a little more speed and MSX compatible bootsectors (and an option to choose between DOS1 and DOS2 bootsectors ).

DskExplorer has some bug in it which causes the files to be unusable if the archive bit of the file to add wasn't set. Solution: set archive bit! This caused some major headaches for me too

If you know something about MSX, you'd be able to work a commandline. So the ancient RDDSK.EXE and WRDSK.EXE should be all you need.

I really don't understand this thread.

I use Win98SE and DiskManager. Every disk image that I create with this tool works perfect with ALL emulators, including NLMSX, my preferred emulator, in any configuration

Just a remark : don't put the MSX-DOS 2 files on the dsk image if this is not really necessary .... and if you prefer MSX-DOS22, then you must also insert the DOS22 rom image in a virtual caetridge slot of the emulator if the emulator is in MSX2 or 2+ configuration

Of course, a Turbo-R config is more easy with MSX-DOS23 as the rom part of DOS 23 is already in the config ! But in this case, don't forget that the disk image format is different ... The solution : a copy of a DOS23 formatted image, kill all existing files and replace them by the files of your choice by using DiskManager !

So, where's the problem ?

Well, I believe Arjan just gave the answer. And indeed, it works. When setting the Archive bit, the files become readable.

btw, this is actually a bug in DskExplorer. MSX itself doesn't care about the archive bit.

I have just created a DSK-image using Diskmanager. It's real fun. I've copied both msxdos1 and msxdos2 systemfiles to the image. In DOS1, after a DIR, all the files are being displayed, but they can't be executed (I DO have given them an Archive attribute). They seem empty. In DOS2, after a DIR, only the systemfiles (both msxdos1 and msxdos2) are being displayed but not the actual demo files. When I type 'snow.com', the demo IS being executed though! And in BASIC, after a 'Files', the files do appear and are usable.

So.....I'm going to find myself another Diskmanager than DiskManager and DskExplorer.

Quote:

Sorry, but I'ma have to agree with Ro here. You guys *ARE* err... Not too bright. Okay, here's how it works... 1) Get NLMSX 0.48 (You prolly have it) 2) Get the Diskmanager the guy from RuMSX made, it's hip... 3) Make a new disk like Ro said, dump your files on it. 4) SAVE the changes you made to the disk. 5) CLOSE the disk manager (Or at least make SURE you closed the file) And that's it, always has worked, always will work... If this does not work for you, you must have the special BillGatesReallyHatesYou Windows version that doesn't allow you to make .dsk images. If that is the case, tell me where to download the files and where to mail de .dsk image and I'll mail it to you. (I'll even test it first.) Good luck, Tobes P.S. Don't be stubborn, try again and follow ALL the steps.

1. Got it
2. Have it
3. Yep, did it
4. Done
5. First closed the file, then the DiskManager

I decided to put the created diskimage up for download. When I boot this image in NLMSX configured as MSX2 and I do a DIR in DOS1, I do see the files. I can't boot them though. They seem empty. Same goes for BASIC. They're simply not usable.

Here's the diskimage I created

Well, adding msxdos2.sys and command2.com to this diskimage really gives a cool effect. In DOS2, after a DIR, you will only see the systemfiles, but you CAN boot the not visible files now. Suddenly, they don't seem empty anymore.....Ain't that nice, huh And when you boot DOS2 and you go to Basic and give a 'Files', the Files suddenly ARE visible. And bootable.