If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#61
|
|||
|
|||
New PC, ME with old BIOS
Bill wrote :-
Sorry to bother you with such an elementary question, but I have 1.5 GB of RAM and .... .... came up with "Sorry, you don't have enough memory" (I think), "Go back and take some stuff out of your autoexec". D'oh! - See "Out of Memory" Error Messages with Large Amounts of RAM Installed http://support.microsoft.com/kb/253912/en-us And it might also explain the issues you had with the 'old' disk. Pity you hadn't mentioned the amount of RAM before g You'll have to edit the system.ini file in DOS if you can't access it in Safe Mode. Failing that, see if you can pull some memory out to reduce it to 512 MB or less. Mart "William B. Lurie" wrote in message ... William B. Lurie wrote: Mart (and Mike): You fellows have gone far beyond the call of duty and I appreciate it and don't want to impose too much farther. Let me be specific: My 98 CD came to me with a PC which was custom made by an 'authorized' assembler of some sort. It's a genuine Microsoft CD and on it is the legend "For distribution with a new PC only", which it was. My ME upgrade CD was given to me by some computer shop some 8-odd years ago, and is obviously a copy, not an original. However, I have not too long ago installed 98 in a VPC under my XP main system, and it accepts the codes. I didn't go on to ME, however. In the past, when I tried to install ME direct from the CD, it told me at the start that it could only be used to upgrade a 98 system. The scientist in me says "Keep on plugging away, find the missing .CAB and files, and make it work". The practical engineer in me says "You've spent too many man-hours, your own and other people's, when you have what is most likely a viable Plan B." I intend to have my guru with the nimble fingers disconnect the main HDD in my PC (because I want to install 98+ME in a safe manner) and unless you two think I'm too much of a coward, I intend to start with a "clean" 98+ME and will see if it takes. Mart wrote: Hi Bill, With further reference to your 5 missing files (which I'd only just spotted - sorry!), I've just been in contact with Mike and concluded that :- depending on how you set-up your original WinMe on the 'old' HDD (can't remember if you said you [over] installed it [a MS or OEM version?] onto an existing OEM [HP?] version of Win98) then the Folder (CABS or Install) MAY NOT EXIST - or be in a completely different location! From a very recent Clean installation I've just done of (MS not OEM) WinMe, where the installation files were copied to the HDD before actually installing WinMe from the HDD itself (The CD-ROM was 'faulty') I have found that WinMe doesn't copy the complete set of installation files to the CABS or Install folder at all, as it would if was installed from the CD. Always said that you learn something new every day on these WinMe NG's!! Is your WinMe CD an MS or OEM version? I take it your 98 CD is OEM. If WinMe CD is MS, and your 98 is a 'special' (compressed) OEM version, then WinMe might not accept the OEM CD as a proof of authenticity and therefore you may have to go down the Plan B (version A) route, i.e. fresh install 98 then attempt the WinMe update. Far too many variables keep creeping in to this 'simple issue' g Mart "Mart" wrote in message ... First of all, note Mikes reply (timed at 12:32 BST today) regarding the much simpler method of a clean install of WinMe - should you need to go down that route. But I don't think we've completely exhausted 'Plan A' - YET!! So I'll address the next items in-line :- Mart, thanks for coming back in. First let me jump down to the USB question. That was a memory slip; the monitor is on its own big multi-connector cable. Phew! - thank goodness for that g I've graduated to where my latest attempts have been with *NO* USB cables connected. Consider it as having only the essential cabling; I even unplugged the Ethernet connector. Indeed, ALL items *MUST* be disconnected. In Safe Mode, there are no errors and no conflicts. There are 4 entries for IDE controllers which I am unable to delete, and Mike says not to fret. Mike's quite correct and on hindsight, perhaps we should have warned you earlier. I didn't answer your query about display adapters and monitors because I think it was prompted by my incorrect association of USB with the monitor. Fair enough. The new PC came with one HDD, containing XP/Home in one partition, and HP's own maintenance and repair software in its "D" partition. I have never removed either of those partitions (nor would I). The way I run or attempt to run WinME is to interrupt the boot process and boot to the Slave drive (which is left over from my erstwhile PC). OK, thanks for that info. For now - assuming it has been physically removed and your WinMe HDD is the only one fitted, it won't be causing any issues. If you read Mike's posts, you'll see that, in shutting down ME, now, I always get an error window about MSGSRV32 where it hangs. OK, for the moment, that's to be expected and probably not too relevant. And in attempting to boot it always complains about 5 files that it can't find, that should be in C:\Windows\Options\CABS. Exactly what files can't it find? Please list all five. Mike had me check Registry to verify that that is where it's directed, and I verified that. It's not the Registry but rather the 'Path' which we are considering here. You need to search (in Safe Mode) for " *.CABS " and (hopefully) find a Folder containing about 20 or so .CAB files (e.g. WIN_15.CAB). Assuming those files can be found, we are (or should be) still in business. However, if you can't find them, then you are up the creek .. as Mike explained earlier and it is definately over to 'Plan B' (but do remember Mikes tip, no need to install 98) I'm pretty well convinced that HP has somehow made it impossible to use the OS on the old HDD even though it boots every time in Safe Mode. I'm about to consider taking another HDD and install Win98 clean on it, from Microsoft's own installation CD, and then upgrade it to ME with my ME-upgrade CD. I can copy back from the questionable HDD those files that I have on it. I don't like giving up on what you and Mike and I have spent so much time on, but maybe it *is* time to move on to "Plan B". See my previous paragraph. Mart snipped Okay, Mike and Mart, I asked about the SATA connectors, spread the cabling to get my arthritic fingers in there, pulled the main HDD power connector, connected the Slave, and started to install 98 from CD. I then had only the blank 7.5 GB drive powered up. It first formatted the 7.5 GB drive, and proceeded to load the files, everything looked good, and it got to 21 minutes to go, and it said it had to restart. Okay, I expected that, and I expected the prompt about "Hard Disk or CD" and from experience, I knew that if I said CD Rom, it would go back to load all the files again. So I selected Boot from Hard Disk, and it clunked and mumbled and came up with "Sorry, you don't have enough memory" (I think), "Go back and take some stuff out of your autoexec". Sorry to bother you with such an elementary question, but I have 1.5 GB of RAM and this "new" HDD is 7.5GB, has *nothing* on it, and........ how do I get out of this CATCH-22? |
#62
|
|||
|
|||
New PC, ME with old BIOS
D**n - Must remember to check for updates before pressing the Send button!
You weren't there when I looked Mike g Mart "Mike M" wrote in message ... Your problem is 1.5GB of RAM. In truth no Win 9x operating system is suited to your system since I now see you mention that it has sata drives for which you will have to try and find Win Me compatible drivers or rather Win 9x compatible chipset drivers for your motherboard. Turning to your RAM, the error message you mention is to be expected. Win Me, like all Win 9x operating systems, can support and use up to 2GB of memory although there are a number of caveats and exceptions to that details of which are contained in the following Microsoft Knowledge Base articles with the first essential reading where more than 512MB of memory is installed. For more details see: MS KB 253912 - ""Out of Memory" Error Messages with Large Amounts of RAM Installed" (http://support.microsoft.com?kbid=253912). The reason is that allocating more than 512MB of RAM to vcache will exhaust all available upper memory addresses and thus prevent them being used for other purposes. This problem is easily fixed as follows: To limit vcache, open system.ini and add the lines [VCache] MaxFileCache=512000 Note that this will still mean that all memory is available to applications but is simply limiting the amount used as virtual cache memory. MS KB 296773 - "Computer May Not Hibernate with More Than 192 MB of Memory" (http://support.microsoft.com?kbid=296773). This makes reference to an updated file vmm.vxd. Unfortunately due to Win Me being out of support this file can no longer be obtained from Microsoft. MS KB 304943 - "Computer May Reboot Continuously with More Than 1.5 GB of RAM" (http://support.microsoft.com?kbid=304943). -- Mike Maltby William B. Lurie wrote: Okay, Mike and Mart, I asked about the SATA connectors, spread the cabling to get my arthritic fingers in there, pulled the main HDD power connector, connected the Slave, and started to install 98 from CD. I then had only the blank 7.5 GB drive powered up. It first formatted the 7.5 GB drive, and proceeded to load the files, everything looked good, and it got to 21 minutes to go, and it said it had to restart. Okay, I expected that, and I expected the prompt about "Hard Disk or CD" and from experience, I knew that if I said CD Rom, it would go back to load all the files again. So I selected Boot from Hard Disk, and it clunked and mumbled and came up with "Sorry, you don't have enough memory" (I think), "Go back and take some stuff out of your autoexec". Sorry to bother you with such an elementary question, but I have 1.5 GB of RAM and this "new" HDD is 7.5GB, has *nothing* on it, and........ how do I get out of this CATCH-22? |
#63
|
|||
|
|||
New PC, ME with old BIOS
Thank you, Mike. First of all, would simply pulling the 1GB RAM strip,
leaving it with 512K, solve the problem? Second, I have to relate that I created a VPC on this machine, and in it I installed Win98 from this identical CD, with no problem. Third, the circumstance which we are discussing rules out any SATA interference as such, since I boot to the 7.5GB EIDE HDD when it is alone on the system. However, you do make a point about 98-compatible drivers or chipsets on the motherboard, but then I refer you to the preceding paragraph, in which I say that the 98 loaded into the VPC on that Master SATA Drive. With that, I look forward to your further clarification. Mike M wrote: Your problem is 1.5GB of RAM. In truth no Win 9x operating system is suited to your system since I now see you mention that it has sata drives for which you will have to try and find Win Me compatible drivers or rather Win 9x compatible chipset drivers for your motherboard. Turning to your RAM, the error message you mention is to be expected. Win Me, like all Win 9x operating systems, can support and use up to 2GB of memory although there are a number of caveats and exceptions to that details of which are contained in the following Microsoft Knowledge Base articles with the first essential reading where more than 512MB of memory is installed. For more details see: MS KB 253912 - ""Out of Memory" Error Messages with Large Amounts of RAM Installed" (http://support.microsoft.com?kbid=253912). The reason is that allocating more than 512MB of RAM to vcache will exhaust all available upper memory addresses and thus prevent them being used for other purposes. This problem is easily fixed as follows: To limit vcache, open system.ini and add the lines [VCache] MaxFileCache=512000 Note that this will still mean that all memory is available to applications but is simply limiting the amount used as virtual cache memory. MS KB 296773 - "Computer May Not Hibernate with More Than 192 MB of Memory" (http://support.microsoft.com?kbid=296773). This makes reference to an updated file vmm.vxd. Unfortunately due to Win Me being out of support this file can no longer be obtained from Microsoft. MS KB 304943 - "Computer May Reboot Continuously with More Than 1.5 GB of RAM" (http://support.microsoft.com?kbid=304943). |
#64
|
|||
|
|||
New PC, ME with old BIOS
Well, M&M, after reading your advice and reporting the news,
I reduced RAM to 512MB and started again, and, mirabile dictu, it started up, asked for the 25 digits, and went almost all the way through the 98 install to 2 minutes to go. And then it did a routine restart, and when it resumed, I got a DOS screen with the message ; "While initiating NDIS, encountered Windows Protection Error. Restart" So I restarted, and it booted past the big 98 Logo screen, and stopped with the same message. Looks like we're almost there.......But now what? William B. Lurie wrote: Thank you, Mike. First of all, would simply pulling the 1GB RAM strip, leaving it with 512K, solve the problem? Second, I have to relate that I created a VPC on this machine, and in it I installed Win98 from this identical CD, with no problem. Third, the circumstance which we are discussing rules out any SATA interference as such, since I boot to the 7.5GB EIDE HDD when it is alone on the system. However, you do make a point about 98-compatible drivers or chipsets on the motherboard, but then I refer you to the preceding paragraph, in which I say that the 98 loaded into the VPC on that Master SATA Drive. With that, I look forward to your further clarification. Mike M wrote: Your problem is 1.5GB of RAM. In truth no Win 9x operating system is suited to your system since I now see you mention that it has sata drives for which you will have to try and find Win Me compatible drivers or rather Win 9x compatible chipset drivers for your motherboard. Turning to your RAM, the error message you mention is to be expected. Win Me, like all Win 9x operating systems, can support and use up to 2GB of memory although there are a number of caveats and exceptions to that details of which are contained in the following Microsoft Knowledge Base articles with the first essential reading where more than 512MB of memory is installed. For more details see: MS KB 253912 - ""Out of Memory" Error Messages with Large Amounts of RAM Installed" (http://support.microsoft.com?kbid=253912). The reason is that allocating more than 512MB of RAM to vcache will exhaust all available upper memory addresses and thus prevent them being used for other purposes. This problem is easily fixed as follows: To limit vcache, open system.ini and add the lines [VCache] MaxFileCache=512000 Note that this will still mean that all memory is available to applications but is simply limiting the amount used as virtual cache memory. MS KB 296773 - "Computer May Not Hibernate with More Than 192 MB of Memory" (http://support.microsoft.com?kbid=296773). This makes reference to an updated file vmm.vxd. Unfortunately due to Win Me being out of support this file can no longer be obtained from Microsoft. MS KB 304943 - "Computer May Reboot Continuously with More Than 1.5 GB of RAM" (http://support.microsoft.com?kbid=304943). |
#66
|
|||
|
|||
New PC, ME with old BIOS
Mike M wrote:
VPC isn't using your system hardware but is emulating some pretty basic stuff, for example the sound and video adapters emulated are both over ten years old. Pulling a memory strip is a short term solution, preferred is to edit system.ini. 98 loaded into the VPC on that Master SATA Drive Irrelevant as I have already said. VPC is emulating a hard drive using a file. Look at Dev.Man. when running any OS to confirm what VPC is offering as devices. Okay, Mike, as you saw later, I did the short-term solution. I now have 512MB of RAM and 98 (this HDD alone on the system) installs almost to completion, halting with the error I more or less quoted, "While initializing NDIS, Windows Protection Error. Restart". As for editing system.ini, I assume you mean from msconfig in Safe Mode if I ever get there.....but how and to what? From a DOS prompt when it halts there, perhaps? |
#67
|
|||
|
|||
New PC, ME with old BIOS
William B. Lurie wrote:
Okay, Mike, as you saw later, I did the short-term solution. I now have 512MB of RAM and 98 (this HDD alone on the system) installs almost to completion, halting with the error I more or less quoted, "While initializing NDIS, Windows Protection Error. Restart". Oh dear, this is may be another hardware problem and could be due to the make/model network card you are using or even possibly your cpu speed. May I suggest you come clean and explain EXACTLY what hardware you are using for this system and again may I remind you that most recent hardware is unsuitable for running any Win 9x operating system other than in a virtual machine. For example see MS KB 312108 "Windows protection error in NDIS with a CPU that is faster than 2.1 GHz" (http://support.microsoft.com?kbid=312108) could be applicable or at least explain a possible cause. See also MS KB273738 "How to Troubleshoot Windows Millennium Edition Startup Problems" (http://support.microsoft.com?kbid=273738). As for editing system.ini, I assume you mean from msconfig in Safe Mode if I ever get there.....but how and to what? From a DOS prompt when it halts there, perhaps? Your choice how you do this. What I consider to be the normal way is to boot to DOS using a floppy and edit it from the DOS prompt as this avoids pulling RAM but seeing as you've pulled RAM then you can do this in a number of ways with Windows running and using MSConfig is one of those ways. -- Mike Maltby |
#68
|
|||
|
|||
New PC, ME with old BIOS
Mike, I am pleased to tell you all that I can,
the info coming from AIDA. It is Compaq Presario Type 061, Model SR1900NX The CPU is Intel Celeron D, 3.2GHz, significantly faster than 2.1 GHz. Video is ATI Radeon Express 256MB. BIOS is Phoenix 3.03 Supports: DMI, APM, ACPI, PnP So far, I've had too much RAM, and my CPU runs too fast. And I'm trying to run a Model-T engine in a Thunderbird. I'm beginning to get the impression that, even though I came within 2 minutes of completing the 98 installation, I really should just live with the VPC. I tried to go the independent-HDD route because I was having trouble getting peripherals to work under VPC. You did seem to hold out some hope, in asking for 'full disclosure',but maybe I only saw what I wanted to see. You did mention that, since I pulled the excessive RAM, "then you can do this in a number of ways with Windows running and using MSConfig is one of those ways." Uh, but I don't quite have Windows running. Can I just start it up and maybe F8 and boot to Safe Mode? Would that take, and what do I do when I get to system.ini? Mike M wrote: William B. Lurie wrote: Okay, Mike, as you saw later, I did the short-term solution. I now have 512MB of RAM and 98 (this HDD alone on the system) installs almost to completion, halting with the error I more or less quoted, "While initializing NDIS, Windows Protection Error. Restart". Oh dear, this is may be another hardware problem and could be due to the make/model network card you are using or even possibly your cpu speed. May I suggest you come clean and explain EXACTLY what hardware you are using for this system and again may I remind you that most recent hardware is unsuitable for running any Win 9x operating system other than in a virtual machine. For example see MS KB 312108 "Windows protection error in NDIS with a CPU that is faster than 2.1 GHz" (http://support.microsoft.com?kbid=312108) could be applicable or at least explain a possible cause. See also MS KB273738 "How to Troubleshoot Windows Millennium Edition Startup Problems" (http://support.microsoft.com?kbid=273738). As for editing system.ini, I assume you mean from msconfig in Safe Mode if I ever get there.....but how and to what? From a DOS prompt when it halts there, perhaps? Your choice how you do this. What I consider to be the normal way is to boot to DOS using a floppy and edit it from the DOS prompt as this avoids pulling RAM but seeing as you've pulled RAM then you can do this in a number of ways with Windows running and using MSConfig is one of those ways. |
#69
|
|||
|
|||
New PC, ME with old BIOS
Further news, Mike....maybe it will surprise you as it did me.
I connected the PC up again, with the partially-installed drive as Slave, my main drive as Master, and rebooted, this time asking to to go to the Slave. I started it up and F8 to the 98 HDD and it booted right into 98, Safe Mode. I'm hastening to tell you this, although I expect that you'll have responded to previous posting before you see this. I did verify that I can access msconfig but you haven't told me what to do there. Now I'm curious as to what will happen if I try Normal Mode... William B. Lurie wrote: Mike, I am pleased to tell you all that I can, the info coming from AIDA. It is Compaq Presario Type 061, Model SR1900NX The CPU is Intel Celeron D, 3.2GHz, significantly faster than 2.1 GHz. Video is ATI Radeon Express 256MB. BIOS is Phoenix 3.03 Supports: DMI, APM, ACPI, PnP So far, I've had too much RAM, and my CPU runs too fast. And I'm trying to run a Model-T engine in a Thunderbird. I'm beginning to get the impression that, even though I came within 2 minutes of completing the 98 installation, I really should just live with the VPC. I tried to go the independent-HDD route because I was having trouble getting peripherals to work under VPC. You did seem to hold out some hope, in asking for 'full disclosure',but maybe I only saw what I wanted to see. You did mention that, since I pulled the excessive RAM, "then you can do this in a number of ways with Windows running and using MSConfig is one of those ways." Uh, but I don't quite have Windows running. Can I just start it up and maybe F8 and boot to Safe Mode? Would that take, and what do I do when I get to system.ini? Mike M wrote: William B. Lurie wrote: Okay, Mike, as you saw later, I did the short-term solution. I now have 512MB of RAM and 98 (this HDD alone on the system) installs almost to completion, halting with the error I more or less quoted, "While initializing NDIS, Windows Protection Error. Restart". Oh dear, this is may be another hardware problem and could be due to the make/model network card you are using or even possibly your cpu speed. May I suggest you come clean and explain EXACTLY what hardware you are using for this system and again may I remind you that most recent hardware is unsuitable for running any Win 9x operating system other than in a virtual machine. For example see MS KB 312108 "Windows protection error in NDIS with a CPU that is faster than 2.1 GHz" (http://support.microsoft.com?kbid=312108) could be applicable or at least explain a possible cause. See also MS KB273738 "How to Troubleshoot Windows Millennium Edition Startup Problems" (http://support.microsoft.com?kbid=273738). As for editing system.ini, I assume you mean from msconfig in Safe Mode if I ever get there.....but how and to what? From a DOS prompt when it halts there, perhaps? Your choice how you do this. What I consider to be the normal way is to boot to DOS using a floppy and edit it from the DOS prompt as this avoids pulling RAM but seeing as you've pulled RAM then you can do this in a number of ways with Windows running and using MSConfig is one of those ways. |
#70
|
|||
|
|||
New PC, ME with old BIOS
So, I tried Normal Mode. Just as I'm sure you expected,
I got that same DOS error message about NDIS......want to clue me as to what I should edit in system.ini? William B. Lurie wrote: Further news, Mike....maybe it will surprise you as it did me. I connected the PC up again, with the partially-installed drive as Slave, my main drive as Master, and rebooted, this time asking to to go to the Slave. I started it up and F8 to the 98 HDD and it booted right into 98, Safe Mode. I'm hastening to tell you this, although I expect that you'll have responded to previous posting before you see this. I did verify that I can access msconfig but you haven't told me what to do there. Now I'm curious as to what will happen if I try Normal Mode... William B. Lurie wrote: Mike, I am pleased to tell you all that I can, the info coming from AIDA. It is Compaq Presario Type 061, Model SR1900NX The CPU is Intel Celeron D, 3.2GHz, significantly faster than 2.1 GHz. Video is ATI Radeon Express 256MB. BIOS is Phoenix 3.03 Supports: DMI, APM, ACPI, PnP So far, I've had too much RAM, and my CPU runs too fast. And I'm trying to run a Model-T engine in a Thunderbird. I'm beginning to get the impression that, even though I came within 2 minutes of completing the 98 installation, I really should just live with the VPC. I tried to go the independent-HDD route because I was having trouble getting peripherals to work under VPC. You did seem to hold out some hope, in asking for 'full disclosure',but maybe I only saw what I wanted to see. You did mention that, since I pulled the excessive RAM, "then you can do this in a number of ways with Windows running and using MSConfig is one of those ways." Uh, but I don't quite have Windows running. Can I just start it up and maybe F8 and boot to Safe Mode? Would that take, and what do I do when I get to system.ini? Mike M wrote: William B. Lurie wrote: Okay, Mike, as you saw later, I did the short-term solution. I now have 512MB of RAM and 98 (this HDD alone on the system) installs almost to completion, halting with the error I more or less quoted, "While initializing NDIS, Windows Protection Error. Restart". Oh dear, this is may be another hardware problem and could be due to the make/model network card you are using or even possibly your cpu speed. May I suggest you come clean and explain EXACTLY what hardware you are using for this system and again may I remind you that most recent hardware is unsuitable for running any Win 9x operating system other than in a virtual machine. For example see MS KB 312108 "Windows protection error in NDIS with a CPU that is faster than 2.1 GHz" (http://support.microsoft.com?kbid=312108) could be applicable or at least explain a possible cause. See also MS KB273738 "How to Troubleshoot Windows Millennium Edition Startup Problems" (http://support.microsoft.com?kbid=273738). As for editing system.ini, I assume you mean from msconfig in Safe Mode if I ever get there.....but how and to what? From a DOS prompt when it halts there, perhaps? Your choice how you do this. What I consider to be the normal way is to boot to DOS using a floppy and edit it from the DOS prompt as this avoids pulling RAM but seeing as you've pulled RAM then you can do this in a number of ways with Windows running and using MSConfig is one of those ways. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
BIOS upgrades - reflashing the BIOS | Bill in Co. | General | 21 | March 25th 08 10:22 PM |
BIOS | Sean | New Users | 3 | March 27th 05 07:30 PM |
BIOS | Sean | Hardware | 0 | March 5th 05 07:27 AM |
bios help | elocm | General | 4 | November 12th 04 09:26 PM |
bios | shep | Setup & Installation | 3 | July 14th 04 09:17 PM |