ProLiant Deployment and Provisioning
1832978 Members
3113 Online
110048 Solutions
New Discussion

Smartstart Scripting Problem

 
Colin Hankin
New Member

Smartstart Scripting Problem

I've managed to successfully deploy Windows 2000 Server and Advanced Server to a ML530G3 using the SmartStart Scripting Toolkit via the iLO and a NC3134 PCI network card. However, I am experiencing problems when trying to use the embedded Gigabit NIC (NC7760).

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
8 REPLIES 8
Colin Hankin
New Member

Re: Smartstart Scripting Problem

Just spotted a typo in my initial message. The server was a ML370G3 and not a ML530G3.

Colin
Gordon Leonard
Honored Contributor

Re: Smartstart Scripting Problem

Since you didn't include any example of your configurations I have attached some sample which may assist you. (see attachment)
Colin Hankin
New Member

Re: Smartstart Scripting Problem

Gordon,

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
Gordon Leonard
Honored Contributor

Re: Smartstart Scripting Problem

On the NIC side of things make sure your using the current NIC BIOS and software. I beleive the new combination uses less resources.

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.

Colin Hankin
New Member

Re: Smartstart Scripting Problem

Gordon,

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


Gordon Leonard
Honored Contributor

Re: Smartstart Scripting Problem

Sometimes it's easier to learn by example especially when it come to the $OEM$. This is what I would to speed up the process. Build a server using SMARTSTART, however; stop the build *prior* to the Windows GUI setup mode. Now get a floppy disk and boot good old MS-DOS. You can now examine the $OEM$ and TXTSETUP.OEM. Let this be your template to your unattended install.
Colin Hankin
New Member

Re: Smartstart Scripting Problem

Gordon,

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
Gordon Leonard
Honored Contributor

Re: Smartstart Scripting Problem

On SmartStart 5.x I would have stopped the process after SmartStart copies the files from the Windows 2000 CD. On reboot you would get the Windows menu selection (where you have 4 seconds to select an option), reboot the server again making sure you have a MS-DOS disk in drive A:. The directory structure should be the same as your creating now (remember the SmartStart is doing the same thing your doing now however itâ s reading from the HD and installing to the HD â thus you will have what looks like duplicate directories). I need to play with SmartStart 6.4 to see if I can still do the same â trickâ