dencorso

Nothing against it. I know it works great. But, then again, no solution using just one HDD protects one against hardware (read HDD) failures, while the two HDDs solution does. It's as easy to recover one of the HDD to the same physical medium as it is when one needs to substitute it, either because of a hardware failure or to get more space (upgrading to a bigger HDD).

Welcome to MSFN, martyna!

Hi, FalleZ. Welcome to MSFN! I hope you stay long with us and enjoy everey single moment of it!

I confirm it. It's now working OK in IE, too. Congratulations, xper, you fixed it! And thanks a whole lot!

Well, while all those methods involving a single physical disk (HDD) are quite ingenious, all of them have downsides. That's why I think the safest way to doubleboot XP and 98SE is to have each on it's own primary partition, each independently bootable, each in its own HDD. And while I nowadays use Grub4DOS to select which I do boot, it can also be done without any boot manager, by using the BIOS ability to logically invert master and slave, that is to say, to set which is the primary boot disk. As each OS is installed in a fully independent way, you can blow any of them seven-ways-to-sunday and still remain able to boot the other, and from it to deploy a previously saved known-to-be-good image of the one you just messed-up beyond all recognition, and be back to a fully blown double-booting machine in less than 30 min. Of course, this way also has a downside: you must have two HDDs to do it. Then again, it has the added advantage that you may partition both HDD's with at least two partitions: each HDD then has a different OS in the bootable partition, backed up by full imaging, and both HDD's have a second identical non-bootable data partition, backed-up incrementally (with XXCOPY) every day. I think this is as safe as you can get, and quite simple to implement, too.

For what's worth, here is my MENU.LST for loading the good old classics with Grub4DOS: This runs OK from a common 1.44 MB bootable MS-DOS 7.10 floppy. Besides the usual DOS files, grub.exe, menu.lst and the raw floppy images, of course, are needed. DRVSPACE.BIN can be removed, and a one line CONFIG.SYS, containing just "INSTALL=GRUB.EXE" should be added.

Warez. On public channels or otherwise.@Leo Natan: Stop acting provocatively! You fully know how to avoid it!

Please avoid posting all in uppercase. Do please read the Rules, esp. Rule #11.

A reboot is needed.

Do give SaverNow a try. It works beautifully in XP.

Or else, install the freeware SaverNow and use it to disable the saver before playing and reenable it afterwards, just by double-clicking its icon on the tray.

VIA 8237 southbridge does not support SATA II speeds (I know your board has a 8237S, and that the latest info I was able to get is on the 8237R, although I doubt the S would be much different from the previous versions...). See: this and this. And about the SATA Driver 220E, see this and this. Bear in mind the 220E driver was written with the 8237's capabilities in mind. Did you try to let SATA disabled in BIOS, and, with the jumper in place on the HDD, then detect it just from within Win 98SE? It might work, though, and if it gets recognized as SATA I, then, the driver would be able to cope with it. Yea, it's a long shot, I know. You don't need the BIOS to detect the SATA drives, unless you're intending to boot from them. In any case, rloew's patch should solve your problem, all right. It doesn't depend on VIA's drivers. However: beware of those Barracudas! See The Solution for Seagate 7200.11 HDDs and numerous other threads in the Hardware Hangout about it. If you just bought it and can exchange it for anything not Seagate nor Maxtor, I'd do it now. The problem is not in the size. It's in the maker. If you have to keep it, I think its advisable update its firmware while it's still OK. Do read the threads on the Hardware Hangout (I know it's a lot to read, sorry!), and form your opinion about it.

OK. Threads merged. Don't do it again.

The king of all Incremental Backup solutions is XXCOPY. Give it a try. It rocks!!! And it's freeware for personal (non-commercial) use.

Yes. rloew is right, once you installed the sata driver for the new drive without the jumper, you must go to safe mode to remove it. Using rloew's demo RAM limitation patch (and removing it afterwards) is the simplest and most reliable way to do it. Once the driver is removed, try to redetect it, since now your drive has the jumper (verify it's placed correctly). The VIA driver should now be able to deal with it. In case it does not work even so, rloew's SATA patch is the way to go. In case you use it, you should remove the VIA driver, however, because it uses ESDI_506.PDR instead. You can find all rloew's programs here (link).

Now, seriously, BenoitRen is right! FAT (16 or 32) is the way to go. Never even give NTFS a second thought.

Use the "Edit" button to add content to your last post, at least until some other member replies. Please do not reply to yourself.

IMHO: No.

Footnote 42 points to a document in Finnish! You surely meant to say footnote 43, haven't you?

@JustinStacey.x: You know you're flame-baiting as well as I do. And I don't like it at all. @all: Don't let yourselves be drawn into yet another OS war. We've already had enough of that!

That should have been the subject line to your thread, not "Question" http://www.msfn.org/board/welcome-forum-t3...tml#entry269823 You're totally right!

@red11: Please don't reply to your own posts. Use the edit function instead.

Here's some great news! I've just received an e-mail from MDGx, in which he says he's OK, just overwelmed by too much work to do. He also says he intends to be back quite soon to MSFN and mentions he received your e-mails, erpdude8, and that he means to add those updates to his site soon and post about them here, as usual.

Support for 1.2 MB MD2HD (5.25") floppies was added with PC-DOS 3.00 and support for 720 kB MF2HD (3.5") floppies arrived only with PC-DOS/MS-DOS 3.20. Older versions will refuse to boot from these formats, no matter what. Thus PC-DOS 2.xx will boot at most from 360 KB floppies (or images), PC-DOS 1.10 and MS-DOS 1.25 will boot at most from 320 KB floppies (or images) and PC-DOS 1.00 will only boot from 160 KB floppies (or images). So I suggest you: 1)Use FDFormat to format a common MF2HD (3.5") to 360 kB (with the high-density tab taped)! 2)Use DiskImage or WinImage to collect a raw image from the 5.25" floppy. 3)Use WinImage to transfer without formatting the raw image to the 360 kB 3.5" floppy you've just prepared! This works in my machine, so it's worth giving it a shot on yours. Good luck! Now, in case your hardware does not accept the MF2HD (3.5") 360 kB created with FDFormat (which lets you produce a floppy perfectly within the original specs), then the best ideia is to boot MS-DOS 7.10 from a floppy, run Grub4DOS and boot the image of the PC-DOS 2.00 from it. In case you decide to go this way I can provide you a more detailed how to (and so can jaclaz who first interested me on the *fantastic* Grub4DOS ). @jaclaz: DCOPY seems interesting, no doubt, and I shall give it some testing shortly. The programs I'm talking about, however, are those that, at lest for me, are proven to work well with those really old versions of DOS, which are very picky as to formatting detail, although they may be tricked into using 3.5" floppies, as long as the FDD plays along.

Probably something like about 55% C, 35% C++ and 10% assembler... if things didn't change too much in the last 10 years. I may be wrong, but I think that's about it. Added comment: @Leo Natan: it seems we were posting at the same time... and you finished first!