ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem using SmartStart 4.80 with Proliant 800 (P02) Server

 

Problem using SmartStart 4.80 with Proliant 800 (P02) Server

I have an old model Proliant 800 (2 x Pentium Pro 200 CPU's version). When I use
SmartStart (Release 4.80) I get to the stage where it asks me to insert the
Profile Disc (Release 4.40 - it's the one that came with this SmartStart)
and then for some reason it can't detect it. Keeps asking me to insert the
disc. I know that the floppy drive works and I also know that the Profile
diskette is OK.

If I use the version of SmartStart that came with the server originally
(Release 3.40) it seems to work OK, except that of course it doesn't support
the installation of Win2K Server.

Any ideas??
Thanks in advance.
Sergio
7 REPLIES
Jake Richie
Advisor

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

Hi Sergio

do a directory of the floppy and see what files are on it.
You should find only SPD.ini on the drive
if not, you can use a dos editor to create file called spd.ini by opening editor and then saving file as spd.ini

or

you can use notepad
open notepad
click file save as:
use SPD.INI
make sure to select file type as "all files"
The early bird may get the worm, but the second mouse gets the cheese.

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

Thanks for the reply.

I have had a look at the diskette and there are several files (keep in mind that this profile diskette has been used on another different server).

The files are:
NDS.OUT
HWDISC-2.DAT
CPQSSBS.BSR
SPD.INI
SWORD.INI
PREOS.DAT

Is your suggestion that I delete all the files except SPD.INI (or create a disketter with just SPD.INI)? Are the other files created when you use the profile diskette?

Once again thanks in advance.
Sergio
Wim Quaedvlieg
Occasional Visitor

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

You could do both:

1. Delete all files except for the SPD.INI
2. Use a formatted diskette and create a (empty) SPD.INI file use i.e. notepad

Victor Pendlebury
Valued Contributor

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

Hi

Something that's nothing to do with your problem but have you upgraded the Bios to the latest version but this is strongly recommended when installing W2000 on older Proliants ...

If Bios is old, you could end up with weird Parity Errors

Vic

PS . does SS4.80 support W2K ?

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

Thanks to all for your reply and apologies that it's taken me this long to reply (been abroad on work).

Unfortunately the the suggestions don't appear to work.

It appears to read the Profile Diskette for a few minutes and then just returns the "Please insert a Server Profile Diskette into A:".

Again, I know that the floppy disk I used is good and the light on the floppy drive lights up. Also, I created the SPD.INI file and this is the *only* file on the diskette.

Any more suggestions/ideas?

Once again, thanks.
Sergio

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

OK I cracked it. It appears to have to do with the RAM. SmartStart worked fine using the original RAM (32MB) or installing only a 64MB DIMM (from Kingston Memory). Using a 128MB DIMM (also from Kingston) caused a problem as too does any other mixture of RAM.

I have spoken to Kingston in regards to this issue and they appeared to be just as surprised as me.

Anyway, it all seems to be up and running now and inserting the other DIMMs appears to cause no ill effect on the system. Hope that all made sense.

Thanks to all again.
Sergio
JAguilar
Frequent Advisor

Re: Problem using SmartStart 4.80 with Proliant 800 (P02) Server

Hi Sergio,

Win2k in particular is not very forgiving w/mismatched memory. You can check on the website for the exact speed/parity recommendations. There are also some rules to follow on certain server as to the allowable configuration. EX. 2x 64Mb Chips in slots 1 and then 3,then 2 x64Mb in slots 2 and 4 and so on. the Service and Maintenace guide for your server should cover this topic.

Hope this helps,
Jose
Semper Fidelis