Fredledingue

Testing the version 4.10.2230: He, no it's not compatible for all computers. My computer seems definetely allergical to anything other than v. 4.10.2222 I'm also curious about the difference between the two since there is less than 24 hours between them. Either all these builds were done at the same time, so to speak, or someone intentionaly falsified the filedates.

I'm gona test that soon.

Buy your dad a 512 Mb or a 1Gb RAM stick. On top of that it will increase the OS stability.

thanks for these clarifications, MDGx.

dencorso Your system works! I have successfuly copied one file from a dvd to the hd in DOS mode. Thank you very much. Next, I'll study the links MDGx gave...

Not sure, MDGx. Last time I checked only 4.10.2222 worked on my computer.

BitTorrent 6.3 may look bloated due to its 3 Mb instaler. However if you install it without the garbage (some search bars and so on) it installs only the executable which is 600 Kb and an uninstall file which is 400 Kb. When I run it, it takes practicaly no resource. v 6.3 allows selected file download. I'm very happy with BitTorrent 6.3 but if you want to play with uTorrent and KernelX, it's up to you.

"Nice" that's all you have to say Ben? I expected you to be more enthousiastic....

Question about USB20DRV What is the last/best/most up-to-date version? This one: http://www.mdgx.com/web.htm#9SU ... or this one, issued at an earlier date (which direct download link has been replaced by the above) Note the file versions are much higher in the latter but it alos contain less files.

uTorrent and BitTorrent are practicaly the same things. I tried first to instal uTorrent on w98 and it failed. I installed BitTorrent 6.3 and it works perfectly with, I think, the same fonctionalities.

Thanks a lot Dencorso! I'll try this as soon as I find time. My drives are IDE. I also noticed my config.sys it's written "device=..." and not "devicehigh=..." and someone posted a command starting with "LH mscdex...". Do "devicehigh" and "LH" make any difference?

Ponch, I can access the dvd drives (there are 2) in windows and even in a dos prompt under windows. It means I can access these drives in DOS when windows is running. I just can't when restarting in DOS mode. So I assume the config.sys settings are correct. They might have to be different in DOS mode perhaps.

I tried SHSUCDX and it doesn't work neither: Cannot find "mscd001" driver. SHSUCDX33 cannot load. It's like DOS ignores config.sys...

According to instruction I have to create a file "dosstart.bat" with the line: MSCDEX /D:mscd001 ("mscd001" is the cd-r drive name mentioned in config.sys) When I restart in MS-DOS, it fails and says: Device Driver not foud: "mscd001" No valid CDROM drive driver selected What should I do?

Thanks for the replies. It's amazing that windows doesn't install this driver by defaut and that no patch or service pack installs it.

When I restart in DOS mode I can't access dvd's in the dvd drive. example: dir g: invalid drive specification See solution on page 2.

I wonder if it's not a problem with io.sys. On large HDD, io.sys must be replaced in DOS mode with an update. Not sure thought. see here Edit: I remember having had this error because user.exe was simply absent at the time of reboot. Find user.exe from another machine, put it on a floppy or second hard drive and, in DOS copy it to C:\WINDOWS\SYSTEM\USER.EXE. HTH

BitTorrent 6.3, up and running on w98se. No problem so far.

I have v4.57. It can open cab files, but couldn't open these ones.

Best wishes to you all!

Yes, I tried to. But 7-zip couldn't open the cab files. I'll give a try with Universal Extractor the next time. Anyway it shouldn't be dangerous to force an install, and it was necessary to run setup.exe to apply the right install procedure, which is impossible to do for a driver without advanced instructions. Normaly w98 should always be able to restart in safe mode. Why it couldn't is beyond me.

That's what I have done with my new Trust drawing tablet tb7300. I think it can be helpful to share my experience and that it can be applied to other hardwares. Anecdote: I easily bypassed the warning by clicking setup.exe but after installation of the original driver my computer crashed and couldn't even restart in safe mode. So even not loading the driver caused a crash. The installation modified a core system file. I had to recopy the system files in dos mode. This distraction made the following steps a bit more complicated but ok. As forcing the driver installation for tb7300 failed I tried an older driver, the tb4200 model. It was specificaly designed for w98 and still available on Trust's website. I installed it and it worked eventhought the tb4200 is a significantly different product and several years older! But I went further: I found the tb7300 files in a folder where they had been extracted during the first attempt as well as the inf file where the installation instructions were saved. Many of the files for the new model were the same as for the old model, some were different but with the same name and a few ones were added. I added the new files and replaced the old files by the new ones except one file which gave a missing export error. Finaly I tweaked up the ini file because the tablet surface didn't match the screen and after a few tests everything worked fine. (Well, almost: the extra functions don't work, but I don't care about that.) So when you see a warning that your hardware is not compatible with your OS, keep in mind that one should never say never.

M$'s legalese and overlapping user agreements is such a mess that I wonder if any high level officer at the company have any idea of what's in there. Let alone understand what's written.

They could have been installed with "drivers". Hardware makers add wierd stuffs with their drivers sometimes.

You can still hire private developers to create updates if you want and share them with us. There are a lot of companies in India or in Russia who will be glad to do it.