MSFN Forum: SOLVED "...file ntfs.sys could not be found..." - MSFN Forum

Jump to content



If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

SOLVED "...file ntfs.sys could not be found..." when trying to install xp sp3 Rate Topic: -----

#1 User is offline   geoslake 

  • Group: Members
  • Posts: 8
  • Joined: 21-January 08

Posted 26 September 2008 - 01:23 AM

hi

I got this message at the end of the drivers loading (with the blue blackground at the beginning of the install procedure).
My cd has sp3 integrated, and I already installed it fine, nlited (services removed etc) and all.
BUT this happens after having integrated hte latest ryanvm 1.0.1 update.
Is it possible for this to have generated such error, as it was released post to latest nlite version ?
Or may it be because I changed something, like, burning speed or so ?
I think i followed the guidelines, integrating the ryanvm pack first, then closing nlite.
THEN I restart nLite and start the nlightment.

thanks

This post has been edited by geoslake: 28 September 2008 - 12:01 PM



#2 User is offline   geoslake 

  • Group: Members
  • Posts: 8
  • Joined: 21-January 08

Posted 27 September 2008 - 03:30 PM

bumpy bump

#3 User is offline   MCT 

  • MSFN Junkie
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,288
  • Joined: 19-May 04

Posted 27 September 2008 - 04:18 PM

when does it occur? during setup ? if so verify that the file is on the cd?
or during bootup?

#4 User is offline   johnhc 

  • MSFN Junkie
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,246
  • Joined: 02-March 08
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 27 September 2008 - 05:37 PM

geoslake,
Have you nLited your source more than once? You should always start with a fresh copy of the CD files/folders.
Enjoy, John.

#5 User is offline   geoslake 

  • Group: Members
  • Posts: 8
  • Joined: 21-January 08

Posted 28 September 2008 - 12:21 AM

View PostMCT, on Sep 27 2008, 04:18 PM, said:

when does it occur? during setup ? if so verify that the file is on the cd?
or during bootup?


Please see beginning of my post.


View Postjohnhc, on Sep 27 2008, 05:37 PM, said:

geoslake,
Have you nLited your source more than once? You should always start with a fresh copy of the CD files/folders.
Enjoy, John.


No, this is with a fresh cd.
I will repeat the procedure and check if it is on the iso, but I'm afraid it's packed as .cab or something...

thanks

#6 User is offline   geoslake 

  • Group: Members
  • Posts: 8
  • Joined: 21-January 08

Posted 28 September 2008 - 01:39 AM

Ok, I had a look at the windows folder after having integrated Ryan 1.0.1 update pack.
Seems every file there ends up with something like .TT_ or .SY_ so the last letter is "hidden".
But that doesn't happen with those :
KSECDD.SYS
ntfs.sys


Yes, this one (ntfs.sys) has its full extension (.sys i mean) AND is lowercase !!

Could this be the cause ?

This post has been edited by geoslake: 28 September 2008 - 01:40 AM


#7 User is offline   Kelsenellenelvian 

  • WPI Guru
  • Group: Developers
  • Posts: 7,754
  • Joined: 18-September 03
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 28 September 2008 - 02:04 AM

Those are CORE setup files, hence why they are uncompressed. (Thatss what the .ex_ means)

I have gotten this issue lately too all you need to do is make that file all in CAPITOLS even the extension.

Setup will then find it.

#8 User is offline   geoslake 

  • Group: Members
  • Posts: 8
  • Joined: 21-January 08

Posted 28 September 2008 - 12:00 PM

yes, this indeed fixed my problem :)
thanks to you

#9 User is offline   olivex 

  • Group: Members
  • Posts: 5
  • Joined: 09-May 09

Posted 09 May 2009 - 01:54 AM

i have the same problem but how to fix it? I see that Ryan's pack are all in lower cases, and nlite seems don't change them.
But last time when I made the ISO there was no such problem. I don't know why.

#10 User is offline   Kelsenellenelvian 

  • WPI Guru
  • Group: Developers
  • Posts: 7,754
  • Joined: 18-September 03
  • OS:Windows 7 x64
  • Country: Country Flag

  Posted 09 May 2009 - 02:04 AM

View PostKelsenellenelvian, on Sep 28 2008, 01:04 AM, said:

Those are CORE setup files, hence why they are uncompressed. (Thatss what the .ex_ means)

I have gotten this issue lately too all you need to do is make that file all in CAPITOLS even the extension.

Setup will then find it.



Try reading through the thread before asking your question again....

#11 User is offline   olivex 

  • Group: Members
  • Posts: 5
  • Joined: 09-May 09

Posted 09 May 2009 - 08:08 AM

View PostKelsenellenelvian, on May 9 2009, 03:04 AM, said:

View PostKelsenellenelvian, on Sep 28 2008, 01:04 AM, said:

Those are CORE setup files, hence why they are uncompressed. (Thatss what the .ex_ means)

I have gotten this issue lately too all you need to do is make that file all in CAPITOLS even the extension.

Setup will then find it.



Try reading through the thread before asking your question again....

I am exactly asking how to "make that file all in CAPITOLS ". I thought nlite should do this.

#12 User is offline   Kelsenellenelvian 

  • WPI Guru
  • Group: Developers
  • Posts: 7,754
  • Joined: 18-September 03
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 09 May 2009 - 09:16 AM

Since nlite seems to be failing to do this simply browse to your folder after the processing stage and before the .iso stage and rename the file manually...

#13 User is offline   olivex 

  • Group: Members
  • Posts: 5
  • Joined: 09-May 09

Posted 15 May 2009 - 07:35 AM

View PostKelsenellenelvian, on May 9 2009, 10:16 AM, said:

Since nlite seems to be failing to do this simply browse to your folder after the processing stage and before the .iso stage and rename the file manually...

What is strange to me is that, sometimes it works. I did the same thing on another PC and it did change file names to capital -- or maybe the nlite version is different -- I am not so sure.

#14 User is offline   1dog 

  • Group: Members
  • Posts: 3
  • Joined: 02-March 09

Posted 06 October 2009 - 11:57 PM

I was searching for this problem, during install I get,

"ntfs.sys" corrupted

so I am directed here. The solution here is change the files so the names are in capital (upper case). I checked the folder and the file is in Upper Case. So I will put it into lower case and see if it works.

Any other tips?

I am using the lastest nlite, service pak 3 and xables Service pak 3 post updates along with the appropriate AHCI drivers for my Intel D975XBX2. Followed the rest of the advice here to the letter.

Off to try it with lower case.

#15 User is offline   1dog 

  • Group: Members
  • Posts: 3
  • Joined: 02-March 09

Posted 07 October 2009 - 12:10 AM

Ok, obviously this is not possible. Not with nlite, tried it and when I unzipped the .iso to check the file was in Upper Case again. Tried imgburn and same thing, but I may be able to adjust it.

#16 User is offline   1dog 

  • Group: Members
  • Posts: 3
  • Joined: 02-March 09

Posted 07 October 2009 - 12:30 AM

Ok, I believe I found the answer:

http://www.msfn.org/board/windows-could-no...s.sys+corrupted


in nlite settings
select 'disable' under the general OEM

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy