- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Solution - network boot disk error when server has...
ProLiant Servers (ML,DL,SL)
1822145
Members
3974
Online
109640
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-01-2004 12:52 PM
12-01-2004 12:52 PM
Solution - network boot disk error when server has over 2gb memory.
I have a HP 580 server with 3gb of memory and a HP 740 server with 8 gb of memory. I was trying to use a network boot disk to ghost the
server image and was running across memory errors due to boot disks having a 2gb memory limit.
I found a network boot disk (below) that did not have the 2gb memory limit error.
Universal TCP/IP Network Bootdisk for Microsoft
Networks
http://www.users.on.net/~driver/bootdisk/index.htm
http://www.users.on.net/~driver/bootdisk/cards.htm (many cards)
This bootdisk solved my 2 gb memory limitation. I was able to boot and ghost both servers. It had the gigabit drivers built in.
--------------
Teledata boot disk had the same error even after I tried this solution: device=himem.sys /numhandles=128
http://tdonline.com/initialpage.htm
---------------
http://www.nu2.nu/bootdisk/network/
I drove home to get an old set of dos 6.22 disks (never got the chance to install and use himem.sys)...
Barts boot disk gave me the same error after I had this message and tried this solution:
The xmsdsk.exe (ramdrive application) does not seem to be able to function correctly on computers with more than 2GB of RAM. I keep
getting the error "XMS get free mem error.".
Yes, I think this is a bug in xmsdsk.exe the author (Franck Uberto) does not have a machine with this amount of memory, so it's not easy
for him to fix it. But here is a workaround: Replace the himem.sys with himem.sys v3.10 (from Dos 6.22), this will provide 64MB XMS
memory as the maximum and xmsdsk.exe will not fail.
jun 16, 2003 - Updated note! Someone mailed me that removing the "/t" parameter for loading xmsdsk.exe solved his problem...
------------------
Both Teledata and Barts bootdisks are superior to the Universal TCP/IP Network Bootdisk but the Universal gets around the 2gb limits on memory without any modifications. great for server booting.
server image and was running across memory errors due to boot disks having a 2gb memory limit.
I found a network boot disk (below) that did not have the 2gb memory limit error.
Universal TCP/IP Network Bootdisk for Microsoft
Networks
http://www.users.on.net/~driver/bootdisk/index.htm
http://www.users.on.net/~driver/bootdisk/cards.htm (many cards)
This bootdisk solved my 2 gb memory limitation. I was able to boot and ghost both servers. It had the gigabit drivers built in.
--------------
Teledata boot disk had the same error even after I tried this solution: device=himem.sys /numhandles=128
http://tdonline.com/initialpage.htm
---------------
http://www.nu2.nu/bootdisk/network/
I drove home to get an old set of dos 6.22 disks (never got the chance to install and use himem.sys)...
Barts boot disk gave me the same error after I had this message and tried this solution:
The xmsdsk.exe (ramdrive application) does not seem to be able to function correctly on computers with more than 2GB of RAM. I keep
getting the error "XMS get free mem error.".
Yes, I think this is a bug in xmsdsk.exe the author (Franck Uberto) does not have a machine with this amount of memory, so it's not easy
for him to fix it. But here is a workaround: Replace the himem.sys with himem.sys v3.10 (from Dos 6.22), this will provide 64MB XMS
memory as the maximum and xmsdsk.exe will not fail.
jun 16, 2003 - Updated note! Someone mailed me that removing the "/t" parameter for loading xmsdsk.exe solved his problem...
------------------
Both Teledata and Barts bootdisks are superior to the Universal TCP/IP Network Bootdisk but the Universal gets around the 2gb limits on memory without any modifications. great for server booting.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP