Unattended Gurus - Problem After Reboot

[=?ISO-8859-1?Q?Andr=E9_Terpstra?=]

Hi,

I am performing XP unattended as so:

1. Boot from a CD (Bootable DOS). (I loaded smartdrv.exe).
2. I manage to load my RAID drivers automatically.
3. The setup copies all files and the reboots.

What happens is that the mbr is not written correctly, and setup does not
resume.

I tried formating the disk, and using fdisk /mbr and no success.

Does anyone have an idea or tip?


Thanks,

Amir.

Did you disable virus protection on the MBR?

Andre.

 

[Amir Miller]

Hi,

I am performing XP unattended as so:

1. Boot from a CD (Bootable DOS). (I loaded smartdrv.exe).
2. I manage to load my RAID drivers automatically.
3. The setup copies all files and the reboots.

What happens is that the mbr is not written correctly, and setup does not
resume.

I tried formating the disk, and using fdisk /mbr and no success.

Does anyone have an idea or tip?


Thanks,

Amir.

 

[Amir Miller]

Do you mean in the BIOS?

It's a Dell machine and I didn't see this option there.

Amir.

 

[Oli Restorick]

When you say you managed to load your RAID drivers, do you mean DOS drivers
for your RAID or Windows drivers?

It sounds like you haven't included your RAID drivers as TEXTMODE drivers in
your $oem$ folder and referenced them accordingly in your answer file.

Mass-storage drivers in unattended setup aren't my speciality and I'm
dreading the day I have to start using them for workstation deployments.

Regards

Oli

 

[Amir Miller]

Good cause for fear.
Actually, I ruled out the RAID as the cause.
I disconnected it and this still happens.

There is a stage after windows finshes coping the files, that it say:
Saving configuration, setting boot options etc. and then reboots and
continues the installation.

My unattended just says flushing data to disk and suddenly reboots, and
obviously this is not enough.

More to come....


Amir.

 

[Oli Restorick]

Can you post your answer file?

Good cause for fear.
Actually, I ruled out the RAID as the cause.
I disconnected it and this still happens.

There is a stage after windows finshes coping the files, that it say:
Saving configuration, setting boot options etc. and then reboots and
continues the installation.

My unattended just says flushing data to disk and suddenly reboots, and
obviously this is not enough.

More to come....


Amir.

drivers

 

[Amir Miller]

Yes:


;SetupMgrTag

[Data]
MsDosInitiated=0
UnattendedInstall=Yes

[Unattended]
DriverSigningPolicy=Ignore
Hibernation=1
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\WINDOWS
FileSystem=ConvertNTFS
UnattendSwitch=Yes
WaitForReboot=No
OemSkipWelcome=1

OemPnPDriversPath=Drivers\SCSI;Drivers\Display\43.51;Drivers\Cib;Drivers\mox
a;Drivers\Nic\Intelpro

[GuiUnattended]
AdminPassword="mxroot"
AutoLogon=Yes
AutoLogonCount=1
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=135
OemSkipWelcome=1


[UserData]
ProductID=QRKY7-7466B-CW46X-HH49Q-M27YJ
FullName="Amir Miller"
OrgName="Philips Medical Systems Technologies Ltd."
ComputerName=*

[Display]
BitsPerPel=32
Xresolution=1280
YResolution=1024
Vrefresh=60

[SetupMgr]
DistFolder=C:\i386
DistShare=i386

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[Components]
accessopt=off
charmap=off
deskpaper=off
dialer=off
freecell=off
hearts=off
media_clips=off
minesweeper=off
mousepoint=off
msnexplr=off
objectpkg=off
paint=off
pinball=off
solitaire=off
spider=off
templates=off
zonegames=off

[MassStorageDrivers]
"PERC 320/DC SCSI RAID Controller" = "OEM"

[OEMBootFiles]
aac.cat
aac.inf
aac.sys
aaccin.dll
aacevt.exe
aacmgt.inf
raidisk1
txtsetup.oem

 

[Patrick J. LoPresti]

Try:

http://www.mail-archive.com/[email protected]/msg00107.html

It is my favorite documentation on txtsetup.oem, but I am a little
biased.

- Pat

 

[Oli Restorick]

That's some great insight there, Pat.

That's found a permanent home in my favourites.

Amir, I believe Pat's article should provide all the information you need.
Cheers

Oli

Try:

http://www.mail-archive.com/[email protected]/msg00107.html

It is my favorite documentation on txtsetup.oem, but I am a little
biased.

- Pat

An update:

I think the problem was with the boot disk I used.
I started using 98 bot disk and I'm past this stage.
I'm now getting stuck on an error from txtsetup.oem.

If anyone has a link to an explenation on how to modify these files, please
post it.

I'm playing with the parameters, but it's a shot in the dark.


]Amir.

 

[Patrick J. LoPresti]

Illegal or Missing File Types Specified in Section Files.SCSI.acc

I tried working out most of the posibilities with the d1 line (\, . , "" at
the end etc.).

In the [Files.Scsi.aac], I left only the driver line, but it still happens.
It's very frustrating.

Are you sure you did this right? Your txtsetup.oem still has the dll=
lines.

I had exactly this problem on one of my systems, and it was resolved

[Disks]
d1 = "PERC 320/DC SCSI RAID Windows 2000 Device Drivers" , raidisk1 , ""

In my case, it was a PERC 3/Di. I commented out the "dll =" lines in
this section:

[Files.Scsi.aac]
driver = d1,aac.sys, aac
catalog = d1,aac.cat
inf = d1,aac.inf
inf = d1,aacmgt.inf
dll = d1,aaccin.dll
dll = d1,aacevt.exe

That almost worked, but the installation eventually stopped asking me
where it could find the .dll and .exe files. I copied them to
$oem$\$$\OemDir, and everything just worked...

- Pat

 

[Amir Miller]

Hi,

It's working!!!
I took the original driver files before I started messing with them, changed
the \ to "" and removed the dll lines.

Thanks for ALL the help.


Amir.

As I said, I tried it just with the driver = line and it still didn't work.

I'll try again.

Amir.

""

at

the end etc.).

In the [Files.Scsi.aac], I left only the driver line, but it still happens.
It's very frustrating.

Are you sure you did this right? Your txtsetup.oem still has the dll=
lines.

I had exactly this problem on one of my systems, and it was resolved

[Disks]
d1 = "PERC 320/DC SCSI RAID Windows 2000 Device Drivers" , raidisk1 ,

""

In my case, it was a PERC 3/Di. I commented out the "dll =" lines in
this section:

[Files.Scsi.aac]
driver = d1,aac.sys, aac
catalog = d1,aac.cat
inf = d1,aac.inf
inf = d1,aacmgt.inf
dll = d1,aaccin.dll
dll = d1,aacevt.exe

That almost worked, but the installation eventually stopped asking me
where it could find the .dll and .exe files. I copied them to
$oem$\$$\OemDir, and everything just worked...

- Pat