Article View: alt.flame.ms-windows
Article #19Re: Memory Limitations Of Windows 3.x
From: Stephen P. Goodman
Date: Tue, 17 Jun 1997 00:00
Date: Tue, 17 Jun 1997 00:00
44 lines
3489 bytes
3489 bytes
Steve Buckley <Stephen@SPBUCK.softnet.co.uk> wrote in article <01bc7a9a$c0460da0$LocalHost@ste>... > All, > > Is there a 16Mb memory limitation to Windows 3.1 or Windows for > Workgroups?? > > i.e. on a 64Mb PC will only the first 16 Mb be used by windows? > I noted your query, which was not answered fully here, and have assumed that you've upgraded your RAM, but Windows doesn't recognize it...? This is a relatively publicly-undocumented problem in Win 3.1x! And it only happens when one upgrades past the 16MB level. It seems that *only during initial install*, SETUP in the target Windows directory is modified to contain an encrypted configuration record pertaining to your machine, while still in character mode. If you run a slow enough PC you can see the message "Modifying Setup.EXE" briefly appear on the basebar. But it ONLY happens at the first install. If you perform subsequent installations on top of the existing one, Setup.EXE's info is not altered with respect to RAM, at least. The only solution is to delete Setup.* from the Windows directory, before starting reinstallation. I knew a fellow who was handling huge files in Word 6.0, so he upgraded his RAM to 32MB. In DOS, MEM reported the full compliment of RAM. In Windows, it still acted like an 8MB PC. He reinstalled Windows, reestablished his VMemory swap file, upgraded his BIOS, replaced the RAM chips installed, all for nothing. We talked to Microsoft, and Dell (the PC maker) extensively. Finally, when I mentioned that perhaps deleting just Setup.* might do the trick - having just seen the slow PC do this at my job - the MS employee said to reinstall from scratch, with no pre-existing install. Of course this latter solution would work, but at the expense of all the previously installed software as well. Deleting Setup.* in the Windows directory and reinstalling on top of the remaining existing installation, is all you need to do in order for Windows to re-recognize the configuration, and your extra RAM. Hope this helps. Stephen Goodman * Download the Loop Of The Week and more! at EarthLight Productions * http://www.primenet.com/~sgoodman/Studios
Technical Details
Message-ID:
<01bc7b59$4949a440$0520a5ce@primenet.primenet.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<01bc7a9a$c0460da0$LocalHost@ste>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f5e03,c34c8f37c3400a8e X-Google-Attributes: gidf5e03,public X-Google-Thread: 112bf7,c34c8f37c3400a8e X-Google-Attributes: gid112bf7,public X-Google-Thread: f8547,c34c8f37c3400a8e X-Google-Attributes: gidf8547,public X-Google-Thread: 113dfb,c34c8f37c3400a8e X-Google-Attributes: gid113dfb,public X-Google-Thread: 1057c8,c34c8f37c3400a8e X-Google-Attributes: gid1057c8,public X-Google-Thread: 110b0e,c34c8f37c3400a8e X-Google-Attributes: gid110b0e,public X-Google-Thread: 1102f1,c34c8f37c3400a8e X-Google-Attributes: gid1102f1,public X-Google-Thread: fe8f2,c34c8f37c3400a8e X-Google-Attributes: gidfe8f2,public From: "Stephen P. Goodman" <sgoodman@primenet.com> Subject: Re: Memory Limitations Of Windows 3.x Date: 1997/06/17 Message-ID: <01bc7b59$4949a440$0520a5ce@primenet.primenet.com> X-Deja-AN: 249137652 References: <01bc7a9a$c0460da0$LocalHost@ste> Organization: EarthLight Productions X-Posted-By: @206.165.32.5 (sgoodman) Newsgroups: alt.flame.ms-windows,comp.mail.eudora.ms-windows,comp.os.ms-windows.misc,comp.os.ms-windows.networking.windows,comp.os.ms-windows.programmer.win32,comp.os.ms-windows.programmer.winhelp,comp.os.ms-windows.setup.win3x,fr.comp.os.ms-windows.win3,fr.c