• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
lawson23

mass storage drivers causing STOP 0x0000007B

16 posts in this topic

Basically I have this added to my sif

[MassStorageDrivers]

"Intel® ICH9 SATA AHCI Controller (Desktop/Server/Workstation)" = OEM

"Intel® 82801HEM SATA RAID Controller (Mobile ICH8M-E)" = OEM

"Intel® 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)" = OEM

"Intel® ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)" = OEM

"Intel® 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation)" = OEM

"Intel® 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)" = OEM

"Intel® 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)" = OEM

"Intel® 82801GHM SATA RAID Controller (Mobile ICH7MDH)" = OEM

"Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)" = OEM

"Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)" = OEM

"Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)" = OEM

"Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)" = OEM

[OEMBootFiles]

iaahci.cat

iaahci.inf

iastor.cat

iaStor.inf

Iastor.sys

Txtsetup.oem

If I try to image a Dell D600 or Dell D610 I get the following:

STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE

If I create the same sif but remove the above from it the devices image just fine.

Any ideas?????

0

Share this post


Link to post
Share on other sites

Ok this is a problem not just for the d600 and d610 but for ANY machine that is not an ahci machine.

There must be something else I need to add to mass storage.

0

Share this post


Link to post
Share on other sites

So are you saying the only way is to add this to my image. There is no way to edit the sif so this works properly.

0

Share this post


Link to post
Share on other sites

Try adding this to your sif under the intel controllers:

"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

0

Share this post


Link to post
Share on other sites

I got the same problem whenever I try to image a computer that doesn't have a SATA drive.

When the system tries to boot into the gui portion of setup after textmode setup, it fails with the bsod.

This is fixed by removing (or commetting) the lines referencing the sata/raid drivers for the intel controllers.

I've added that line for the PCI controller, hope it works.

edit: ok that seems to work.

Edited by pengo
0

Share this post


Link to post
Share on other sites

Ok I followed the instructions posted by jaclaz and now I have a problem.

Basically I took this opportunity to add two mass storage device drivers to my system one is a scsi driver for LSI.

nlite worked fine and created me a iso image.

I took the dir where it made the modifications and used this to create a new RIS base image.

Now when booting and trying to RIS I get

File Symmpi.sys caused an unexpected error (21) at
line 3540 in d:\xpsp\base\boot\setup\setup.c.
press any key to continue

Anyone have any ideas on how to either fix this or go back and start over on this?

0

Share this post


Link to post
Share on other sites

Ok I again followed the instructions posted by jaclaz.

But this time I did not do the LSI and only did the AHCI drivers alone.

nlite worked fine and created me a iso image.

I took the dir where it made the modifications and used this to create a new RIS base image.

Now when booting and trying to RIS I get

File iastor.sys caused an unexpected error (21) at
line 3540 in d:\xpsp\base\boot\setup\setup.c.
press any key to continue

Anyone have any ideas on how to either fix this or go back and start over on this?

0

Share this post


Link to post
Share on other sites

I use BARTPE and do the following:

Create a Nu2menu that has a button for sata and a button for non-sata. point the sata button at a batch file that executes winnt with the sata .sif, and the non-sata button at a batch that executes winnt with the .sif that has the lines removed.

The 2 seperate batches each looking something like this with different .sifs specified:

start /wait %YOURPATH%\i386\winnt32.exe /s:%YOURPATH%\i386 /unattend:%YOURPATH%\i386 \YOURFILE.sif /syspart:c: /tempdrive:c: /makelocalsource /noreboot

Edited by iamtheky
0

Share this post


Link to post
Share on other sites

@lawson23

Just for the record, jaclaz DID NOT post ANY instructions. :no:

He posted a link to a specific thread on this board giving the instructions AND specifically troubleshooting issues deriving from them.

Wouldn't it appear "logic" to post on the referenced thread:

http://www.msfn.org/board/Integration-of-I...ve-t107504.html

a report and request for help/troubleshoot? :unsure:

Maybe the Author of the method knows a bit more about his creation than a guy simply pointing to it...:whistle: and there are possibly more probabilities he would notice the issue on "his" thread than on this one.

:)

jaclaz

0

Share this post


Link to post
Share on other sites

Actually you posted instructions saying

Read here:

In response to my issue well if you see I did not jump right on this because these are not concerning RIS.

Well since this was the only semi logical path that I have received in a year I decided to finally give it a shot.

The reason for not posting in that article is because this is not related to RIS which is my issue.

So instead of going half way off topic in that thread because it is not concerning RIS I decided to repost in my thread where I asked the specific question. You know instead of taking offense you could of just said hey maybe you should ask someone in the other post as they might know.

Say I'm a user reading this thread with my original issue. How would I understand my post with the errors if I didn't refer to the instructions you posted? Doesn't it make logical sense for someone to mention where he got the information he tried.

I'm sorry for you feeling offended by my previous post but I had no intentions of offending you, until now. I don't know why you take such offense to someone stating that what you suggested did not work.

Either way I fixed the issue myself I believe. I will post with what I did for others to follow or gather information from.

0

Share this post


Link to post
Share on other sites

Following this thread:

http://www.msfn.org/board/index.php?showtopic=13173&st=0

I edited my txtsetup.sif file adding the following:

txtsetup.sif

[SourceDisksFiles.x86]

iaahci.cat = 1,,,,,,3_,4,1,,,1,4
iaahci.inf = 1,,,,,,3_,4,1,,,1,4

iastor.cat = 1,,,,,,3_,4,1,,,1,4
iastor.inf = 1,,,,,,3_,4,1,,,1,4
iaStor.sys = 1,,,,,,4_,4,1,,,1,4
iastor.sys = 1,,,,,,3_,4,1,,,1,4

mpixp32.cat = 1,,,,,,3_,4,1,,,1,4

symmpi.inf = 1,,,,,,3_,4,1,,,1,4
symmpi.sys = 1,,,,,,4_,4,1,,,1,4
symmpi.sys = 1,,,,,,3_,4,1,,,1,4
symmpi.tag = 1,,,,,,3_,4,1,,,1,4

[HardwareIdsDatabase]
PCI\VEN_1000&DEV_0621 = "symmpi"
PCI\VEN_1000&DEV_0622 = "symmpi"
PCI\VEN_1000&DEV_0624 = "symmpi"
PCI\VEN_1000&DEV_0626 = "symmpi"
PCI\VEN_1000&DEV_0628 = "symmpi"
PCI\VEN_1000&DEV_0030 = "symmpi"
PCI\VEN_8086&DEV_2922&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2829&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_282A&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor"

[SCSI.load]
symmpi = symmpi.sys,4
iaStor = iaStor.sys,4


[SCSI]
symmpi = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)"
iaStor = "Intel(R) ICH9 SATA AHCI Controller (Desktop/Server/Workstation)"
iaStor = "Intel(R) ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)"
iaStor = "Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation)"
iaStor = "Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)"
iaStor = "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"
iaStor = "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"
iaStor = "Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"
iaStor = "Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)"
iaStor = "Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)"
iaStor = "Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M)"
iaStor = "Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"
iaStor = "Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"

Then I added these driver files to the I386 dir:

IAAHCI.CA_

IAAHCI.IN_

IASTOR.CA_

IASTOR.IN_

IASTOR.SY_

MPIXP32.CA_

SYMMPI.IN_

SYMMPI.SY_

SYMMPI.TA_

These are the drivers created from the nlite change but I believe they are just the drivers and then they rename the prefix from like .cat to .ca_ and .sys to .sy_ and .inf to .in_.

This I'm not sure of because I just used the drivers obtained from the nlite build I mentioned above.

I have successfully tested this with a Dell Precision 650 LSI SCSI but have not been able to test with a AHCI pc yet.

0

Share this post


Link to post
Share on other sites

I am not offended at all. :)

What I was trying to convey is that I know next to nothing about driver integration, that Fernando1:

http://www.msfn.org/board/index.php?showuser=58937

knows a lot about the topic, and that it is unlikely that he will notice this thread/your request for help, and thus it is not probable he might help you.

I presume that posting in there a request for help pointing to this thread may be the "right" thing to do. ;)

:hello:

jaclaz

0

Share this post


Link to post
Share on other sites

Well I'm glad we cleared that up. Either way thank you jaclaz as it didn't resolve the issue the posting did give me the things to do futher searches on to find the resolution. Bottom line without your post I would not have this fixed and my above solution was just verified on a dell e6400 which is AHCI.

Update:

6400 copies files so it now sees the drive but later on during the install when it reboots it fails on the startup with blue screen and loops.

Edited by lawson23
0

Share this post


Link to post
Share on other sites

Well I figured out my last issue which happened to be the 07b bsod error.

Basically in post one I had these files in this location [OEMBootFiles]:

iaahci.cat

iaahci.inf

iastor.cat

iaStor.inf

Iastor.sys

Txtsetup.oem

I took these files and put them in my RIS_Base_Image\$oem$\$1\drivers\sata\001\*.* folder and then added this path to my sif file in RIS.

Then took these files and added them to RIS_Base_Image\$oem$\$1\drivers\sata\002\*.* folder and then added this path to my sif file in RIS.

MPIXP32.CAT

SYMMPI.INI

SYMMPI.SYS

SYMMPI.TAG

Txtsetup.oem

OemPnPDriversPath="PREVIOUS OTHER DRIVER PATHS ENTERED;\Drivers\SATA\001;\Drivers\SATA\002"

I could not use these files placed in i386 folder not sure why but would get the same bsod when using this version created by nlite in the drivers location:

IAAHCI.CA_

IAAHCI.IN_

IASTOR.CA_

IASTOR.IN_

IASTOR.SY_

MPIXP32.CA_

SYMMPI.IN_

SYMMPI.SY_

SYMMPI.TA_

dell e6400 ahci laptop now RIS successfully and verified.

0

Share this post


Link to post
Share on other sites

Interesting report. :yes:

Happy you managed to find the solution to this problem. :)

jaclaz

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.