|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (7 bit)
Join Date: Apr 2005
Posts: 83
|
XP boot woes..
can i get some help with an XP sp2 pro boot issue please,,A friends pc was left on for 3 days or so, comes home, mild panic and hard shutdown,,So currently he,s stuck with it booting to login and then restarts.! Eliminated: Vid card,ram,,monitor,cpu.
So far we tried a repair and it requires the asms file from sp1? cd,,Default search option for it is "globalroot\device\cdrom1\1386" or E:,,,However the cdrom is on d: ,,there is no e:,,what is the correct format for it to read the cd with the 1386 file.? D:\? Any advice appreciated....Reaper |
|
|
|
|
|
#2 |
|
Member (10 bit)
|
D: or d: there should be no difference you just have to enter correct letter!!!
__________________
I am always doing that which I can not do, in order that I may learn how to do it. |
|
|
|
|
|
#3 | |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 36,460
|
Quote:
http://www.lavasofthelp.com/articles/v6/04/06/0901.html |
|
|
|
|
|
|
#4 |
|
Member (7 bit)
Join Date: Apr 2005
Posts: 83
|
Thanks glc but thats not the problem,,During a repair it wants the sp1 asms file which is located in 1386 folder,,,not having a sp1 disk as a standalone, i have a copy of the asms file from sp1 which i even burnt to a disk,,but it still fails to see it,,I belive the path should read D:\1386\asms for it to read the disk,,however that dose not appear to be the case,,Am i using the correct Parameters for it to be seen if i use the Path as above?,,,bloody hell this is frustrating.
wondering if it is a sp2 issue?, or would it be standard for it to look for the asms file from sp1, during a repair? Regards,,,thanks in advance.. LOL,,,glc you have been here from the begining of PC Mech,,,You guys helped me or wrecked my life about 6 years ago,,encouraged me to upgrade an old k7 as i remember,,now thats my whole damned life,,upgrades,,gaming,,repair and upgrade all my mates machines,,Hehaaa,,Thanks. Nice that i have found my way back to these great forums..So i know u guys can help me.. Last edited by Reaper; 04-14-2005 at 06:44 PM. |
|
|
|
|
|
#5 |
|
Professional Cow Tipper
Join Date: Jan 2002
Location: Enid, OK, U.S.A.
Posts: 2,855
|
Just a thought here, and it may not help, but you asked about the parameters you were typing in, as to whether they were correct or not. I see you are calling that folder 1386. You do realize that the number one is actually an "i", right? It should be I386 with the letter I in front, not a number one. I don't know if this is the problem, but if you are telling it to search at 1386 it can't find it because it doesn't exist....I386 does however.
|
|
|
|
|
|
#6 |
|
Member (7 bit)
Join Date: Apr 2005
Posts: 83
|
JUPPY, Thanks,,,im such a loser...Ta. I,ve seen it,,I know it ,but didint take any notice while looking for the path.Seems i wanted the problem to be bigger than it really was...
|
|
|
|
|
|
#7 |
|
Professional Cow Tipper
Join Date: Jan 2002
Location: Enid, OK, U.S.A.
Posts: 2,855
|
Heheh....yeah, we've all done that at some point. Thought an i was a 1 or a number 0 was a letter O. It happens.
|
|
|
|
|
|
#8 |
|
Member (1 bit)
Join Date: Apr 2005
Posts: 1
|
I've been getting a similar thing. One question, did you get an AutoUpdate when you last shut down?
2 machines in our house (completely different hardware, both running XP SP2 (beta, but updated since)) had an update over the last couple of days and have been "boot looping" ever since. Anyone else seen anything similar? |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|