• 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.
aviv00

Guide - Install WinXP From HDD or USB Drive Or CD

55 posts in this topic

Tried both method 1 and method 2 with the same result: installation fails while loading Windows NT filesystem (ntfs.sys). Nice BSOD says that windows is shut down to prevent a damage of my computer, blah-blah-blah, run chkdisk /f.

CHKDISK says that there are no problems.

ntfs.sys on setup disk has the same date and size as the one on the working OS.

Could anyone help me?

PS.

BSOD says "*** STOP: 0x0000007B (...)", so I tried to use a modified ntdetect.com as it was advised above. Result is the same however.

Edited by crusoe
0

Share this post


Link to post
Share on other sites

You say:

e. copy whole asms folder to c:\I386

but the image "after mapping and copy the files set the files (steps 2/3)" doesn't show a I386 folder.

You might like to update this image to avoid confusion :blink:

0

Share this post


Link to post
Share on other sites
Tried both method 1 and method 2 with the same result: installation fails while loading Windows NT filesystem (ntfs.sys). Nice BSOD says that windows is shut down to prevent a damage of my computer, blah-blah-blah, run chkdisk /f.

CHKDISK says that there are no problems.

ntfs.sys on setup disk has the same date and size as the one on the working OS.

Could anyone help me?

PS.

BSOD says "*** STOP: 0x0000007B (...)", so I tried to use a modified ntdetect.com as it was advised above. Result is the same however.

sorry dont have any idea what cause that

u use raid or ahci maybe ?

Edited by aviv00
0

Share this post


Link to post
Share on other sites

BSOD says "*** STOP: 0x0000007B (...)", so I tried to use a modified ntdetect.com as it was advised above. Result is the same however.

sorry dont have any idea what cause that

u use raid or ahci maybe ?

It's certainly not raid, but AFAIK ahci has something to do with usb - and SATA disks. Should I do something special if the installation target is SATA?

0

Share this post


Link to post
Share on other sites
It's certainly not raid, but AFAIK ahci has something to do with usb - and SATA disks. Should I do something special if the installation target is SATA?

0x0000007b means "unaccessible boot device".

In the case of a SATA device, please read as:

0x0000007b I miss the appropriate SATA drivers for this device

Read FAQ #3 here:

http://www.msfn.org/board/faqs-t116766.html

Add the BTS driverpack (or add the specific SATA driver) to the source.

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

  • Recently Browsing   0 members

    No registered users viewing this page.