Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Guide - Install WinXP From HDD or USB Drive Or CD


  • Please log in to reply
54 replies to this topic

#51
crusoe

crusoe
  • Member
  • 2 posts
  • Joined 20-October 09
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, 20 October 2009 - 05:02 AM.



How to remove advertisement from MSFN

#52
doveman

doveman

    Advanced Member

  • Member
  • PipPipPip
  • 391 posts
  • Joined 22-August 05
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:

#53
aviv00

aviv00

    Windowaizer

  • Member
  • PipPipPipPipPip
  • 988 posts
  • Joined 02-April 07
  • OS:none specified
  • Country: Country Flag

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, 10 November 2009 - 09:55 AM.


#54
crusoe

crusoe
  • Member
  • 2 posts
  • Joined 20-October 09


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?

#55
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,657 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

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/...qs-t116766.html

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

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users