setupdd.sys error 0x000000BE

[mattozan]

Can anyone help me get past this error?

During text-mode setup I get a stop messege saying that setupdd.sys has tried to write to read-only memory and the system has halted. Error code is 0x000000BE

Drivers load OK, setup files are copied to the HD, and the contents of $OEM$ is copied to the HD. Then as soon as it starts initializing something (hive...inf?) I get this system stop.

I'm installing to a clean NTFS partition that is formatted first thing in the installation. I only have three apps plus install.cmd, cmdlines.txt, and regtweaks.reg in my $OEM$ folder.

My winnt.sif file is attached (with some info XXX'd out...)

winnt.sif

[GreenMachine]

Welcome to MSFN, mattozan!

First create a CD WITHOUT WINNT.SIF, CMDLINES.TXT, and anything elst that is not listed in the failsafe list of the Current Hotfixes page of the Web Site. Once you have the basic CD working correctly, add your tweaks and apps.

Let me debug XPCREATE, not user files and reg tweaks, and remember, please, everyone, walk before you run: Make a functioning baseline CD, and then add your customizations.

[mattozan]

Thanks--good to be here!

I have successfully made a failsafe CD. Having done that, I thought I'd try adding KB839643. Then I kind of went nuts and also added in everything else that seemed cool...

So, taking your advice to heart, I've removed all the xtras and will slowly add them back in one by one to isolate the problem.

I've just started by adding SP1A (my CD had SP1) and that worked fine. Next I'll try just adding a basic winnt.sif to install KB839643 through install.cmd and see how that goes.

I'll be back when/if that 0x000000BE error crops up again.

[GreenMachine]

@mattozan: Caught you! Unfortunatly, trial and error is often the best debugging technique. I do want to mention that P1A is (supposedly) the same as SP1, less the MS Virtual Java Machine, and some indeo codecs. It has nothing new, and in general, people prefer to install SP1 to SP1A (well, at least I do ... )

Do post when you find the trouble maker!

[Radimus]

I dunno if this is of any assistance, but Mine has started to do so since I added a few lines into my winnt.sif. Before this change the iso worked fine.

specifically:

ExtendOEMPartition=1

FileSystem=ConvertNTFS

NTUpgrade=No

Repartition=Yes

it happens right after the textmode "Setup is copying files..." finishes

The problem seems to be caused by the following file: setupdd.sys

An attempt was made to write to read-only memory

I made the image this morning from a sp1a base and all patches as of today.

I'm rebuilding it now to try again, and will research the above items

[GreenMachine]

Much as I hate to admit it, I got the same error last night. It was late, and I was trying to "cut some corners". I re-used some repacked installers from XPCREATE ... Fortunatly. we had a power outage, I went to bed, and a "clean" run this morning is fine. Still don't know which was the guilty party, but I just slapped myself for not listening to me, and forgot about it.

[Radimus]

I rebuilt the image and changed a few items in the winnt.sif and all is well.

On to CD2: MSO2k3

CD1 unattended WinXPSP1+

CD2 unattended MSO2k3+

CD3 antivirus, other misc apps, Drivers, Regtweaks, and sysprep

creating corporate Disk images has never been so easy...

[GreenMachine]

... creating corporate Disk images has never been so easy...

Hmmm. I hate to burst your bubble, but please re-read the EULA you agreed to upon installation, and contact me.