dencorso

No Judges, granted. But plenty of Referees holding Assizes.

Read this sticky, and the links pointed therein.

It's complicated... FAT-32 always uses 3 sectors for the boot structure, however: 1) If the OS is MS-DOS, LBA0 is the boot sector that loads IO.SYS and LBA6 is its backup; LBA1 is the FSInfo sector and LBA7 is its backup; LBA2 has the second part of the boot code (and is pointed to from within the code in LBA0) and LBA8 is its backup. 2) If the OS is Win 2k/XP/2k3, LBA0 is the boot sector that loads NTLDR and LBA6 is its backup; LBA1 is the FSInfo sector and LBA7 is its backup; LBA2 is blank (or has whatever contents it had before), and so is LBA8! LBA12 has the second part of the boot code (and is pointed to from within the code in LBA0), and has *NO* backup! 3) If the OS is ReactOS, LBA0 is the boot sector that loads FreeLoader and LBA6 is its backup; LBA1 is the FSInfo sector and LBA7 is its backup; LBA2 is blank (or has whatever contents it had before), and so is LBA8! LBA14 has the second part of the boot code (and is pointed to from within the code in LBA0), and has *NO* backup! See: And this Tutorial about ReactOS

As I said, the Intel Application Accelerator should be all you need. But I'm far from being the best member to advise you about it, since I've never used it myself, because I'm a faithful AMD user, and so I've never needed it... until this year, when I began working on a netbook based on the ICH6. However, I'm just starting with it, so it's too soon for me to tell you anything about the IAA from personal experience. Other members here have far more experience with the IAA than myself, and are invited to kindly chime in.

The freeware versions (including the DOS versions) are here: mbrwizard. A good description of v. 1.52/3 options is here. V. 2.00 is similar in use to them.

Great. Thanks! BTW, here's the identification I promised. I had posted it above, but moved it here, just to make sure you saw it.

By do you mean... 11. Run this command: C:\windows\rundll.exe setupx.dll,InstallHinfSection DefaultInstall 132 C:\System Restore\290700UP.INF ?

Fileden is blacklisted by most antiviruses, at present, so that's a bad choice. You shouldn't have used it, in any case, after knowing there's malware around. So, please, do upload it again at a safer place. Try uploaded.to, if you want a suggestion.

You need, at least, RLoew's KERNEL32 2GiB Seek Bug Patch, too. Get it at his site. But you should PM him, in case you wish the German version.

Not any banana recognized as such in the northern hemisphere, but apple bananas instead, and that's too bad, because they have apples aplenty, and apple bananas taste very like apples...

USBoot. YMMV, though.

Nah. There's too much booze and weed behind the green glass door for them to keep at it, let alone carrying any task well.

That squares with my own results: less than 450 GB are enough for them to give the "not enough memory" error. Since they also work OK up to 320 GB, there's just a 130 GB gray zone, between 320 and about 450 GB remaining to be explored for their true limit to be fully known. As I think I said elsewhere, the maximum cluster number accepted by scandisk and defrag (about 26,4 million clusters) would lead to a predicted maximum size (= 865 GB) much larger than that, so, while the maximum cluster number *is* a factor, it's not the only one that can prevent their correct working.

Install FineSSE in Win.ini, and see what happens.

Yours is a great result! However, my point about the DR FORMAT is that it allows one to set cluster sizes with the option /C:clsize. Obviously it's a moot point with so big a partition. But it would be nice to know whether it also can work OK with your enormous partition. I don't think we'll have another chance to establish that any time soon. So, if you can, please do test it. Moreover, DR DOS is a fully different code base, So, you may perhaps avoid the cosmetic error about size upon execution, even if it's harmless. But, in any case, you'd need a quite smaller partition to test setting cluster sizes with the option /C:clsize. BTW, does the Win ME DOS scandisk.exe manage to work with your enormous partition? Also BTW, if you give me MD5 hashes for those format programs, I may help you pinpoint where did they come from.

11.5.9r620 is out for some time, already. Just a friendly heads up!

Lorrie Morgan & The Beach Boys - Don't Worry Baby ... this is another cover that's way better than the original!

It's a VIA C7-M / VIA VX800U (with a VIA Chrome9 HC3 inside)... So it's a no go.

@j80r51m: Don't *ever* double-post!

KernelEx doesn't solve any issues addressed by FineSSE, nor vice-versa. They cater for different problems. They may be used together, if needed, IMO, although I don't think such a set-up has been tested yet.

Welcome to MSFN, jumper! And thanks for FineSSE! I'm sure many of our members will be much happier now, due to your hard work!

The link given is to v. 1.2.0.0... v. 1.2.1.0 only added some command-line switches and changed the default behavior to try to delete the keys on opening, which results in a windows error, when they're already deleted for good. I had it, but after using it for a very short time downgraded back to v. 1.2.0.0, to avoid the annoying windows error on opening. It has not been saved by the internet archive, but I may look for it on my old backups, if anyone really wants it. It's not worthy the effort, though, IMO, since it adds nothing really useful to v. 1.2.0.0.

That means the Airis Kira 740 would be the perfect netbook to run Win9x/ME in? That's great news! It can be bought used for about US$ 100 nowadays, around here, rebranded "Positivo".

Welcome to MSFN, victorhugo289! And thanks for the info!

Sure. MSFN shall become 10 years old on August.