- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Smartstart Scripting Problem
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
Forums
Discussions
Discussions
Discussions
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
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
11-12-2003 02:44 AM
11-12-2003 02:44 AM
Smartstart Scripting Problem
When the COMMAND.COM executes NETBIND.COM, I receive the following error message:-
MS-DOS LAN Manager v2.1 Netbind error 33 unable to bind.
I suspect that the problem is connected to the DOS driver that I am using. I've tried using both the b57.DOS and q57.DOS drivers but both drivers produce the same error message. Am I using the correct driver or is there a problem with my PROTOCOL.INI file?
Any offer of assistance will be greatly appreciated.
Colin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2003 02:51 AM
11-12-2003 02:51 AM
Re: Smartstart Scripting Problem
Colin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2003 02:25 AM
11-13-2003 02:25 AM
Re: Smartstart Scripting Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2003 10:20 PM
11-17-2003 10:20 PM
Re: Smartstart Scripting Problem
Thank you very much for your assistance, with the help of the files that you sent me I have been able to identify and resolve my initial problem.
However, I have now encountered another problem which I would appreciate your assistance with.
When my AUTOEXEC.BAT file executes 'net start', I receive the following error message:-
ERROR 8: There is not enough memory available
Again, any assistance that you can provide will be greatly appreciated.
Regards,
Colin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2003 12:12 AM
11-18-2003 12:12 AM
Re: Smartstart Scripting Problem
http://h18023.www1.hp.com/support/files/server/us/download/15133.html
http://h18023.www1.hp.com/support/files/server/us/download/18320.html
I don't know what your loading from Config.sys and Autoexec.bat - Load DOS high, remove SmartDrv, EMM386 (not HIMEM.SYS you need this to load DOS high). Try to load items in the Autoexec and Net batch files into high memory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2003 02:05 AM
11-19-2003 02:05 AM
Re: Smartstart Scripting Problem
Thanks again.
Loading the Net batch files into high memory resolved the memory problem. I then encountered a problem when attempting to connect to the network share (Error 53: The computer name specified in the network path cannot be located). This was resolved by downloading the latest version of Q57.DOS as suggested. I was then able to connect to the network share and commence the W2K installation. After copying about 60% of the files, the file copy froze and I lost connection to the network share. I managed to resolve this problem by adding the Microsoft SMARTDRV.EXE utility to my boot disk.
The network build successfully completes the file copy and reloads. Once it has reloaded, I receive the following error message from the Windows 2000 Server Setup screen:-
The manufacturer provided file that setup is trying to use is corrupted or invalid:
Line 1 contains a syntax error.
Setup cannot continue. To quit setup, press F3.
I've added the nicdrvr.dll to I386/$OEM$/$$/SYSTEM32, q57w2k.cat/inf/sys and to I386/$OEM$/TEXTMODE. Do I need to amend UNATTEND.TXT and/or TXTSETUP.OEM?
Regards,
Colin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2003 05:33 AM
11-19-2003 05:33 AM
Re: Smartstart Scripting Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2003 04:10 AM
11-20-2003 04:10 AM
Re: Smartstart Scripting Problem
I'm not sure about what you are asking me to do. Can you please clarify? I will be using the HP Proliant essentials foundation pack version 6.20. At what point of the SmartStart process do I stop? If I stop during the SmartStart process, where will $OEM$ and TXTSETUP.OEM be located? Is 6.20 OK or should I use a 5.xx version? Do I stop before I load the W2K Server CD? If I have to stop after the W2K Server CD has been loaded, at what point do I stop? If I stop during the W2K installation, will the files be on the C: drive?
Apologies for so many questions but I'm quite new to HP Proliants/Windows.
Thanks.
Colin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2003 08:57 AM
11-20-2003 08:57 AM