dencorso

I really don't think it's worth the trouble, since you cannot avoid the 4.38 GiB DVD±R limit due to its maximum capacity. While CDFS (ISO 9660) Level 3 can go up to 8 TB, by using multi-extent files, even then you'd be limited by the lenght of the media to 4.38 GiB for DVD±R or, at most, 7.96 GiB for DVD±R DL. Or do you intend to explore the uncharted (and costly) world of Blu-Ray?

AFAIK, the version number change is by Maximus-Decim, not LLXX. I don't believe she'd ever do it. But it's indisputable that version 2230 is her modified 2225.

The other possibility is you have a partially broken hardware. The Lite-On DH-20A4P is a great burner, I happent to have one too, and mine burns all types of media from CD-R to DVD+R DL. Now, I had a LG GSA-4163B Super-Multi CD/DVD Burner which served me well for many years, burning numerous CD-R, CD-RW and DVD-R. One day I decided I needed even bigger media and I bought a cake of Verbatin DVD+R DL (Singapore), the very best media of this type, and found out, much to my chagrin, that the burner was only able to make coasters of them. Intrigued, I then bought two DVD+R discs and it dully made coasters of them, too. Now, that was proof it had stopped working properly, because I had tested it, just after I bought the burner, with DVD+R discs, and at that time it worked OK. So it simply lost its ability to burn +R media at sometime in-between, but continues working OK with -R media up to now. I've replaced it by a LG GSA-H55N Super-Multi CD/DVD Burner, and now I'm able to burn DVD+R (both SL and DL) again. Of course, I did try various methods of cleaning the 4163B, to no avail, and updated its firmware, again to no avail, before throwing the towel and buying a new burner.

Use instead v. 6.6.1.15a, which is the same Nero update but has less bundled things to avoid the installation of. You can download it here.

Well, in my experience, Gape's uSP works well with > 1 GiB RAM, but one must first reach the right configuration without it, then save MSDOS.SYS, AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI and WIN.INI, then apply Gape's uSP, reboot, restart in MS-DOS, restore those saved files and reboot again. At this point one should either apply RLoew's RAM Limitation Patch or use the method of HIMEMX.EXE (renamed to HIMEM.EXE), xRayeR patch, Xeno86's vcache and XMSDSK (and in the latter case, Win 9x will not see more than about 1160 MiB of RAM, but the rest can be used in a ramdisk). I personally prefer to use RLoew's RAM Limitation Patch patch, in combination with RLoew's non-XMS Ramdsk, which is much more stable, but not free. The main problem with Gape's uSP with machines having lots of RAM lies, AFAIK, in the way it tweaks SYSTEM.INI, not in the updates it contains (but Gape's tweaks are OK for less than 1GiB, of course).

Before anything, do get the manual, or at least the specs of your burner and confirm it should, in fact, be able to burn DVD±RW. And post the exact brand and model, just in case.

Maybe you should add a DVD+RW to your testing set, as well, just to be on the safe side (I do favor DVD+RW over DVD-RW, but either would be equally OK, here).

@PROBLEMCHYLD: Read the "Micro How-to" in post #2 of my thread on > 137 GB HDDs for which there is a link to the right of my signature, here below. @Prozactive: That's easy: just the version number! A binary comparison never lies! As for the reasons why, that's a long history... I answered briefly that question here. If you wish to have a full view of the history behind the version numbers conundrum, and have time for it, do read the whole original LLXX topic.

Eureka! You have found it. Thanks for finding this, it was driving me crazy. Wow! Great catch, submix8c! Way to go!

When a file that exists inside VMM32.VxD is present also in the %windir%/SYSTEM/VMM32 folder, the version in that folder gets loaded instead of the one packed inside VMM32.VxD. Moreover, during the compilation of VMM32.VxD, windows strips the version info from the VxDs it'll then pack together, so that when you extract any VxD from inside VMM32.VxD, you'll get a file lacking the version info, although otherwise perfect and functional. So, a binary comparison with the original VxD is the only way to confirm the version of a VxD extracted from VMM32.VxD: if you compare it to the right original file, it'll be byte-by-byte identical, except for lacking the version info section. I use BeyondCompare to do it, but that's not a free software, so maybe you'll prefer to use some freeware alternative to it... In order to see a list of all the VxDs inside VMM32.VxD (or extract some or all of them, if you so want) you'll need Clive Turvey's VxDLib. VxDLib can also repack files into VMM32.VxD (but this one feature I never did test myself)... And to see what VxD are loaded and running in your system, in real time, you'll need the fantastic APSoft VxDView. And, last, but not least, The Truth About VMM32.VXD is the best article about VMM32.VxD I've ever found, and much worthy of being read.

I got no experience with Win 95 MSBATCH.INF. All my experience is from 98+, but here're my two wild guesses about what may make a difference, and yet be invisible in plain view. Bear in mind they're just guesses. There are no blank lines either before or after every section title. Are you sure these blank lines are irrelevant? The section titles in your file are all fully uppercase... Are you sure the MSBATCH.INF processor is case insensitive?

Great work, LoneCrusader! This thread is now added to the Important "Stickified" [Pinned] 95/98/98 SE/ME Topics.

1-28-2010 * Windows 95 added to this thread's title. Added under "Supported Software, Games + Hardware": * Windows 95 2.1GHz CPU Limit BROKEN!: http://www.msfn.org/board/index.php?showtopic=141402 Enjoy.

Sammy Hagar - Piece of my Heart

Banned members who return will be banned again. No exceptions.

Active Killdisk. The freeware edition should be enough.

No. I use IE6 on 98SE and IE7 on XPSP3. It took me long to make IE7 feel and look right to my tastes. Yes, it can. It accepts the MS Office 2007 Compatibility Pack gracefully and then can tackle even the latest formats. See my thread about it here.

Why would I? IE7 and Office 97 can do all I need them to. I upgrade only when unavoidable.

You're right, of course. I mixed things up somehow while I searched my archived files looking for the oldest versions of your programs. I stand corrected. The Int30 method worked right away, and I used it until you found and fixed the last bug in the SYSENTER method (in 05/10/08), and then I switched over to the SYSENTER method, and remain using it to this day.

You have the precedence in the discovery, for sure. The oldest archived version of the RAMDSK3S I have in archive is dated 07/14/2008, and that was already the 1st beta!!! Wow! And, yes, as you know, I remain using precisely that method (from the three you offer) in my day-to-day usage of your current Non-XMS RAMDSK32: it's reliable, and windows never notices it's there!

Yes. BackUp. The blind, sector-by-sector image is a bullet-proof b-a-c-k-u-p. After you create the image, you can remove and reinstall AVG7.5... If all goes well, there's no need for the image. If things get fubar, then you'll simply redeploy the image and get back to the state the machine had before you removed AVG, and can try again.

Did you refer to the Full Disclosure article, RLoew? Did you actually look at the example code mentioned?

Thanks for the detailed info. So, let's see: --------- 1) According to the List of Intel Chipsets, your i850/ICH-2 chipset has a limit of 2 GiB RAM at the maximum. It uses PC800/600 RDRAM. 2) The online Manual of the Dimension 8100 agrees with that, and mentions that the biggest memory module it accepts is of 512 kiB. Rambus memory (=RDRAM) needs all the slots populated to work, so whatever the arrangement used, it must have a stick in every slot. --------- My suggestion would be to replace both 64 MiB sticks by 512 MiB sticks, resulting in jumping to 1.25 GiB RAM. Here's how to procced: 1) Add a MaxFileCache=393216 to the [vcache] section of your C:\WINDOWS\SYSTEM.INI and save it. 2) Shut the machine down. Disconnect physically the machine's power cable from the wall power outlet. 3) Wait for at least 10 minutes, to allow the boards capacitors to discharge. 4) Substitute the required modules. Here are detailed instructions on How to replace RDRAM. 5) Reconnect to the power outlet and turn on the machine. The BIOS should recognize the memory change and test it. The system should now boot and then start windows, so that, all going well, you should then get back to windows. --------- Good luck!

Well, welcome Andrew T. and BenoitRen! It's great to have you here in this thread! But, now, can either or both of you answer the originally posited question? To me it's a mystery why MSBATCH.INF isn't working as intended by LoneCrusader... can you perhaps enlighten us, please?

Since the memory is paged anyway and the memory page is 4 kiB, 4096 (= one page) is the maximum value that makes any sense, IMO. I use half that because I couldn't find a test condition capable of showing any difference between those two settings, and chose the lower arbitrarily. Notice that the ChunkSize is expressed in bytes, not kiB. The definitive reference about the ChunkSize is Adrian Rojack's Optimization Guide. All this have been said in the thread I pointed to, so I'll stop repeating them from this post on. C'mon: it's all pointed to in the > 1GiB thread... Start reading!