0x7B : SP2 against SP1

  • Thread starter Thread starter Dietmar
  • Start date Start date
D

Dietmar

Hi all,
after building hundreds of images with Embedded SP2 and SP2, I noticed
something strange:

Sometimes arrives 0x7B on a normal IDE harddisk before FBA(image build
with SP2),
but this image,
build with the same components of SP1,
runs, with exact the same hardware there, without any problems through
FBA.

This happens not vice versa.

Did you notice a similar behavior of SP2 and is this perhaps depending to
the Intel chipset or only one bad driver in SP2?
Then, I think, it must be a driver, which is loaded early in boottime.

I would be very glad, if someone could clearify this.

Nice to hear from you all

Dietmar
 
Dietmar,

I believe I have had this happen, if you mean the following:

1) Using SP1, run TAP.EXE and develop a configuration in Target
Designer. FBA boots fine.
2) Now load that config into SP2, build it, boot to FBA - you get STOP
7B.

(This was on an Intel 865 chipset board.) I believe this is because
something in the boot files from SP2 (NTDETECT.COM, NTLDR, etc.) is no
longer compatible with the SP1 components. If you re-run TAP and
recreate the config in SP2, all is well.

-- Don
 
Hi Don,

I thought, that if you put a *.slx file
from SP1 to SP2, that all the new components from
SP2 are now put in the new image.
But this seems not to work without problems.
And using Tap.exe is not a solution, if you build
a generic image.
And it sounds,that even a new dependency check will not help in this case.


Nice to hear from you
Dietmar

PS: Will that mean, that you cant use any *.slx
file, build with SP1, in SP2?
 
Back
Top