- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Memory Above 132 Kills OS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2001 04:00 PM
тАО06-16-2001 04:00 PM
Memory Above 132 Kills OS
Note: An associate of mine had this same problem. He discovered that if you create a partition using NT instead of Win2k, he was able to install Win2k with RAM above 132 MB after upgrading his controller firmware.
Selecting NT from the utilities after you have already intalled Win2k will crash the OS.
Since I already have Win2k running with 132MB will I have to re-install with my associates solution or does Compaq have a fix available??
Thanks,
Glenn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2001 04:00 PM
тАО08-18-2001 04:00 PM
Re: Memory Above 132 Kills OS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2001 04:00 PM
тАО12-28-2001 04:00 PM
Re: Memory Above 132 Kills OS
ustek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2001 04:00 PM
тАО12-28-2001 04:00 PM
Re: Memory Above 132 Kills OS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2001 04:00 PM
тАО12-29-2001 04:00 PM
Re: Memory Above 132 Kills OS
------------------------------------------------------------------------
1. Upgraded array controller to the newest ver. (ver.4.43)?
--------------
I successfully installed W2KS on 2x166MHz/RAM132MB(128MB I'd rather say). But I have SMART 2/P firmware ver. 2.06. Smartstart 5.2 did not suggest to upgrade it. The only one piece of hw I had upgraded was the mother board. (E12 ver. 08/17/98.)
I'll try to find the latest upgrade (4.43 I've read on this forum) and post the results.
=================
2. Memory size over 132MB kills w2k. ???
-----------
Memory size must not be a problem.
I believe that system cpq?cfg may not report memory size correctly to w2k.
Also it's not clear how W2k is killed. are you able to start install?
are you able to complete the text part of install?
are you able to complete install at all?
does the system finds a file to boot?
========================
Try to analyze the condition at which the boot fails.
I would recommend to hit F8 and go to a detailed boot process.
(Like the VGA mode in NT)
I'll be conducting more research on w2k memory issue this holiday.
**************
One more thing I discovered yesterdayon this forum. It is the Advanced mode of the CFG utility.
When you have fisrt screen (after you hit F10) depress CTRL+A. You'll get the Advanced mode. Then go to EDIT+VIEW.
You'll see Memory. there are two choces: auto and Standard.
Play with them. It may help.
Regards,
ustek@hotmail.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2001 04:00 PM
тАО12-29-2001 04:00 PM
Re: Memory Above 132 Kills OS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2001 04:00 PM
тАО12-29-2001 04:00 PM
Re: Memory Above 132 Kills OS
"Hardware Malfunction
Call your hardware vendor for support
The system has halted"
I don't think this is a windows error screen. It does not include any more info on this screen than that. I take out the extrra memory and run the CFG again to bring it back down to 132 and volia! W2K starts with no problems. The momory I am using is from another excect system that has been running with Novell for years with out fail. I also noticed others in this forum having the same memory limits and have not found an answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2002 04:00 PM
тАО01-04-2002 04:00 PM
Re: Memory Above 132 Kills OS
May be it will reveal anything.
did you try install w2k after system erase?
when you do full system erase you wil be quided by smartstart till final install.
Moreover, smartstart will prepare all necessary drivers for you to install w2k.
Ustek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2002 04:00 PM
тАО01-15-2002 04:00 PM
Re: Memory Above 132 Kills OS
I tried to make the most of this old box.
The reason was "slow speed memory" error.
When I removed "slow memory" install went through.
Then I added the memory back and everythyng runs fine.
Resolution: get rid of any error prior to installation of w2k.
Then make changes you like.
I did not upgrage Smart 2/P array yet. Still running ver.2.08
ustek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2002 04:00 PM
тАО08-06-2002 04:00 PM
Re: Memory Above 132 Kills OS
P.S. To downgrade a controller, edit the config.sys file of the firmware upgrade disk. Put a /x on the rompaq.exe line.