dencorso

Steve has passed away. May he rest in peace. The world has lost a great man, who had the gift of making things happen. Things will never be the same again.

Opera 10.10 works beautifully, and does not need KernelEx. It can use Java 5 and Flash 9 also flawlessly.

Caheman is OK, in principle. It should cause you no problems. As for RLoew's patcher, you won't see anything, if you're waiting for a menu or whatever. What you have to do is, at the dos prompt, type: Patchm /M and then hit enter. /M is a command-line switch, that should be given to the patcher program when you run it.

system.cb is in %windir%\, the same folder system.ini also is in. you must create the [vcache] header in it, then add the MaxFileCache under it. Rephrasing RLoew's latest question: what're the sizes of your system.dat and user.dat?

Happy Birthday to both!

The complete catalog of RLoew's patches and related products is available here.

Gape's uSP 2.1 did it for you. When you applied it it set MaxFileCache=393216 under [vcache] for you. BTW, it's Gape, not Gabe... But your system will probably have problems with Safe Mode, unless you add a [vcache] setting in system.cb, too. If you do it, you won't need Xeno86's vcache.vxd. Now, while Gape (and me too) considered 393216 the best value to be used, you can use more, if you wish, up to 524288 (both in system.ini and in system.cb).

Of course not, although Microsoft do seem to be now doing their best to finally sweep it under the carpet. There's still a huge amount of information on the MS site relating to Windows 98 though, even though the Windows Update service for it has been withdrawn. Like any OS, Windows 98 will only truly die when there is no computer left in the world running it, and that's a very long way away yet! These two posts quoted above are from another related thread, but I think they fit well here, too.

With all due respect, Joe, I disagree. I'm fully aware that: However, the coercivity and the strenght of the magnetic field used need not necessarily to be matched. On the contrary, using HD media to record low density formats works OK, although it's an overkill. Media with higher coercivity will hold weaker magnetizations just as well as it does higher magnetizations, but the other way round is not true. So trying to format DD media to 1440 kiB results in bad clusters galore appearing fast, in a matter of a few days at most, in the very rare cases they don't appear right away, during the format operation. But formatting HD media to 720 kiB is just as safe as formatting DD media, although perfectionists would first apply a bulk demagnetiser to preformatted floppies. Experience (not just my own) confirms this is the case, and as I said above, the appearance of bad clusters in HD media occurs at about the same rate (which is slow) for any format from 160 kiB to 1680 kiB. I imagine ED floppies behave in the same way, accepting both HD an DD formats just as well as 2880 kiB. However, since I've no experience with ED floppies, I leave this last comment as just a speculation, that needs experimentation to confirm.

Sure looks like it! But since you remain active, it's still time to change that...

Welcom to MSFN!

I agree with jaclaz. I've been formatting 3.5" diakettes to all possible formats, from 160 kiB to 1743 kiB for the last 5 years, if not more, without any unusual reliability issues. Of course, floppies can develop bad clusters, with passing time, but they do that at the same rate, regardless of being formatted to 1440 kiB or not. Formats using more than 80 tracks are slightly more prone to developing bad clusters, but then one is using an area of the floppy that the manufaturer didn't intend to be used. Sony and Maxell floppies are very reliable. However, nowadays, it's getting difficult to find new, unopened, boxes of Maxells. But Sonys and Imations are still plentiful.

I confirm it. I'm using RLoew's original patch, combined with the pair of Steven's patches Joe recommends. Since the latter are both one byte patches, what I did was to apply RLoew's patcher to the KB311561 IO.SYS, and then add the 0x206C and the 0x3A01 patches by hand. It works great.

The above pic is from this arstechnica article, FTW.

Here's a direct download link to IOSYS.ZIP, from RLoew's original post in the Phantom Drive Letter thread.

You didn't search the forum, did you? PassingBy is not around anymore, but BenoitRen remains with us, so if the above info is not enough (but it *is* a good start), you should ask him.

With all due respect, I must disagree. grub4dos is no headache. Anyone on the 9x/ME who isn't confortable with DOS or command-line is in the wrong place. IDE --> SATA and SATA --> IDE adapters are a *big* headache. Some do work but extensive testing is needed.

@MagicAndre1981: As soon as I manage to do it I'll post it. Menwhile I've see the same crash happen in at least 7 different machines at work, all of them having plain vanilla XP SP3 installations with IE8. The site for getting the crashes is the main page of the UOL news portal. It's content varies by the day, but clicking on news links and then in news links inside the newly arrived-at page, sooner or later causes a crash. And disabling the "automatic crash recovery" reults in either the messages in the 1st post or in IE8 closing suddenly. This also seems to be a bug known to MS, but fixed only for latter versions of windows (see: KB979665).

This thread reminds me of a movie called Camille...

Yes. But also do reproduce your final menu.lst as a quote, for the benefit of future readers. Glad its solved.

OK. Do the following: 0. Make the SATA HDD bootable to DOS 7.10 (the one in Win 98) 1. Download this version of grub4dos-0.4.4-2009-10-16.zip and extract just grub.exe from it to the root directory of the SATA HDD bootable partition. 2. Create a text file in the root directory of the SATA HDD bootable partition containing the following: and rename it to menu.lst. 3. Reboot. 4. When you get the DOS prompt, type grub and hit <enter>. ... If the machine then boots from your old HDD, just like it used to, then all that remains is to automate it. If not, then it's time to start experimenting. This is one of the many ways it might be accomplished using grub4dos. Of course, jaclaz would prefer another, perhaps simpler way. There're many. There's also an online manual for it which is good enough for you to get the gist of it: Grub4dos Guide. You might also like to read this recent thread. Whatever happens, do keep us posted.

Yes, but we have to test if it works with RAID Highpoint whatever (or have you the same kind of card?) True enough (and no, I don't have that kind of card... But if I did we'd loose more than half the fun, wouldn't we?). Thanks , but be aware that this may sound as an "argumentum ad verecundiam" : http://en.wikipedia.org/wiki/Argument_from_authority Well, according to the Wikipedia, a good "argumentum ad verecundiam" must meet at least two conditions: While 1. is certaily true, 2. is complicated... On the matters we deal here usually there may even be perhaps local consensuses, but anything near universal consensus is a unattainable myth, to say the least. But, solving the problem, which I'm confident will be solved, will certaily validate my argument, so I'm confident I'm safe.

I do it in my main machine everyday. Grub4dos will exchange the disks all right and C: will be assigned to the HDD whence it booted last (so your old HDD bootable partition will end up as C:). That said, I leave you in the very capable hands of jaclaz, who is the one from whom I first learned about grub4dos.

Great info, Multibooter, thanks! I do have a question, though: what are the VIP and PID of the Imation Model No. SD USB M3?