dencorso

As stated in Rule #1a, this is not a warez site, nor do we discuss warez. Hiren's Boot CD, whatever version of it, *is* warez, as is the Mini XP contained in some versions of it and, therefore, neither is acceptable subject for discussion. Two mentions of Hiren's in the same thread are two too many... @morokat and @exogenesis: consider yourselves warned! Thread closed.

For emulating up to 4 SCSI CD/DVDs.

That's Daemon Tools. Sure. and Version 3.47, to be precise.

Welcome to MSFN, kcdude! I'm confident you'll enjoy it here.

BTW, is 3.5.18 the very last 3.5.x?

No, don't do it. Keep it as a memento from the times there was no 98SE. A CD doesn't take that much space. BTW, I'm glad you solved you problem!

See also: FAT - Wikipedia

+1. I think loblo just hit jackpot! It's the least complicated way to achieve the desired result, and needs no software installation at all, and uses only free software! Great!

Now I've got it! What you need is an intelligent movie splitter! Of course, both 7-Zip *and* WinRAR can span their archives into < 4GiB files. Of course, a simple file splitter, like hjsplit, can hack any binary into < 4 GiB pieces. [And, of course, either operation would have to be performed on NTFS (or ExFAT), to have a place to hold the file > 4 GiB you'd like to split, to avoid truncating it, so it cannot be done from Win 9x/ME, for sure, since Win 9x/ME would cause the truncation, even if using a NTFS (or a presuntive ExFAT) installable file-system driver.] But, in any case, neither will allow you to actually *use* the pieces to view them, when they're pieces of a movie! So, please, stop dancing arround it and open a new thread, this time with the right subject, will you?

Yes, the 4 GiB (-1 byte) limit is intrinsic to the design of the FAT filesystem (no matter whether 12, 16 or 32, but only FAT-32 has volumes big enough to hit it), since it's due to representing the file size, in the directory structure, as an unsigned double-word (= 32 bits), resulting in a [(2^32)-1] max value, since the counting is from zero. No, even if you use UDF or NTFS, Win 9x/ME internal structures also use 32 bits numbers internally, so the OS itself is limited to a 4 GiB (-1 byte) max file size, and only a huge amount of careful patching might solve it. So, for all practical purposes, no, it cannot be done. RLoew and Xeno86 confirmed this in this thread of not very long ago. Nothing changed, nor is likely to. Of course, an ExFat driver may be written, but it'll also be limited to 4 GiB (-1 byte). Sorry.

While I do agree with CoffeeFiend, *the* external command to have at hand, in case you wish to stick to a .cmd/.bat is NirSoft's nircmd, which is useful for much more than that.

Threads merged. @sureshmicro2007: Don't double post, please.

There's no RAID option, AFAIK, sorry. But he should enter BIOS setup, set the Flash Cache module to "OFF", then set the SATA Operation to "ATA". If it works for Win XP, it should work for Win 9x, too. A little more detail on this here. Of course, after doing this, he should follow my instructions in my previous post, and hope for the best.

You did not install the uSP yet, right? If so, do the following Boot UBUNTU and go to c:\Windows\System, rename VMM32.VXD --> VMM32.NXT and VMM32.BAK --> VMM32.VXD, then go to c:\Windows\System\VMM32 and delete VMM.VXD, VMM.BAK, VCACHE.VXD and VCACHE.BAK. Now boot to DOS and reapply RLoew's patch, and don't forget to use the /M command line switch. Reboot, and windows should start correctly. Whatever happens, report before proceeding.

OK. So, if starting from scratch, you should let the installer go on to the moment it attempts to reboot by the first time, then follow RLoew's instructions: So, now make sure the system is booting OK. Now you apply the uSP, and don't let it reboot again or let it try to rebbot, but it'll not succeed. Then: 1. Boot UBUNTU and copy the following files to a temporary directory, say, c:\SAFEKEEP: VMM32.BAK and VMM32.VXD from c:\Windows\System and VMM.VXD, VMM.BAK, VCACHE.VXD and VCACHE.BAK from c:\Windows\System\VMM32 2) Go again to c:\Windows\System and rename VMM32.VXD --> VMM32.OLD and VMM32.BAK --> VMM32.VXD 3) No go to c:\Windows\System\VMM32 and delete VMM.BAK, VCACHE.VXD and VCACHE.BAK. Be sure *not* to delete VMM.VXD. 4) Boot true DOS and reapply the RAM Limitation Patch. 5) Boot Windows again, and it should just work! 6) From Windows Explorer, navigate to c:\Windows\System\VMM32, highlight VMM.VXD, right-click on it and, from the menu, from the menu, select Properties, then Version: it should say that you have VMM.VXD file version 4.10.2226. If you reached this point and all is well, now it's time to get the full version of the RAM Limitation Patch, because the Demo is time-limited, and your system clearly requires it, since just modifying SYSTEM.INI got us nowhere.

Welcome, RLoew! Your valuable adivice is much needed in this thread. osiff is using ATA (=IDE Mode), not AHCI. That's why I think he'll be in compatibility mode until adding either your patch or a (rumored) SATA driver included with the IAA. I wouldn't know whether threre really are Intel drivers for SATA, because I'm a true believer in AMD.

Of course. The uSP reverts the patch. You'd have to patch again, after installing the the uSP... If that's what you intend to do, let me explain how to perform the repatch, before you attempt it. So let's discuss a little, before you go ahead and install again for the third time. You shouldn't do all things in a haste. Solve the boot problem first., then the SATA problem, then start thinking about updating. Your hardware is sufficiently new to make all things require careful planning and the creating of good fallback strategies, before each step. Now, if you're going to reinstall from scratch, do it and then test RLoew's patch properly. If it works well, you should be able to boot normally, not just in safe mode. Then you should make a system image backup, and follow it by installing the Intel Application Accelerator. Keeping logs (outside the problem machine, at this point) of everything that was done and whel also helps a lot. There's a definete probability that you'll need RLoew's SATA patch, besides the RAM Limitation Patch, IMO.

It'll work in compatibility mode, at best, IMO, because there's no driver for it. It's slow but should be enough for solvin the problms with > 1GiB RAM. However, once that's solved you should install the Intel Application Accelerator, to give it a proper performance. Yeah. That should work.

Go figure! Great finding! Thanks a lot. You rock!

Yes. Boot from a DOS diskette or CD and clean up the mess by hand from DOS. Then you'll be able to boot OK again. BTW, what part of... ...did you fail to understand?

OK. Let the revised system.ini in the machine, and be sure to install RLoew's patch from DOS, with the /M command line switch. I just found the Inspiron 1525 [link I] [link II] [link III] specs... Is your HDD IDE (aka PATA) or is it SATA? If it's SATA, that may be an issue, too. And RLoew has a patch for that, too, if needed. But that may not be necessary if the chipset is Intel, because, then, the Intel Application Accelerator has you covered... well... sort of.

Dan del Santo - Life's Full of Surprises

Same here. In any case, I took the opportunity to move this thread to the proper forum...

Your file was in the correct DOS format, and, IMO, had only correct entries. I gave it some minor revisions, but I doubt any of them will make any difference... but do give it a try, please. If this proves to be insufficient, do give RLoew's RAM Limitation Patch Demo a try. SYSTEM_REVISED.zip

You should work from true dos, to dispel that doubt. It's quite easy to create a dos boot cd. Yes, the patch you can download is a demo. The full version is not for download, and not for free, but its value far outweights its price. But I do think MaxFileCache=16384 and MaxPhysPage=30000 should be enough to boot your machine, with 2GiB RAM. So, if you want, do attach your zipped system.ini to your next post, so that I can ensure it's in proper dos format or correct its format and attach it back. Then you may delete it from the windows directory and put the corrected one in its place, and then try again. You can move files around and zip/unzip them without any problem using ubuntu (or any other unix-family OS), but editing text files can give problems, so we ought to check this first.