X-13 Posted January 30, 2012 Posted January 30, 2012 (edited) [i know this isn't Bill's fault... But it's fun to blame other people.] Blargh. I have to install XP onto a computer, then smartclient is over to CC3 to replace a broken computer temporally. [Yes, I know... It should be Win7. I don't make these decisions.] Do you think it works? [censored] no, it doesn't. Windows has to be the only OS where it's possibly to get the BSOD while trying to install it.[or whatever variant is in other OS's [comma? no comma? I are good grammarer.]] First, I thought it was because Ubuntu server edition was on it. So I installed Vista [With no problems.] Tried XP again... BSOD. Seriously, Windows? You're going to BSOD DURING THE [censored] INSTALL?! I hate you. Roll on [non-specifc data in the future] when I/we don't need to bother with this anymore... In other news: First thing Monday morning. Still drinking my first coffee. Given 2 bottles of pear cider by the head. Not sure if he's awesome, my job is awesome or I'm that damn awesome... Edited January 30, 2012 by X-13 I accidently the sentance. I'll try not to do it again.
irsprint84 Posted January 30, 2012 Posted January 30, 2012 have you set the sata mode in the bios? think legacy from achi 1
BenABF Posted January 30, 2012 Posted January 30, 2012 Had this on an old HP, turned out to be faulty memory. Might be worth just doing some diagnostics. 1
X-13 Posted January 30, 2012 Author Posted January 30, 2012 It came with XP installed, and all I've done in the BIOS is turn off "halt on no keyboard". I doubt it's the memory... But I'll test it tomorrow. [i'm lounging around at home... LIKE A BOSS!]
Domino Posted January 30, 2012 Posted January 30, 2012 [or whatever variant is in other OS's [comma? no comma? I are good grammarer.] that's no comma, that's a fully operational battle-apostrophe! ..and no, it's not needed 2
Oaktech Posted January 30, 2012 Posted January 30, 2012 I hate you. Roll on [non-specifc data in the future] when I/we don't need to bother with this anymore... it's pretty specific...08/04/2014 Microsoft Support Lifecycle 1
bondbill2k2 Posted January 30, 2012 Posted January 30, 2012 have you set the sata mode in the bios? think legacy from achi I'm guilty of this mistake more then once, the first time I sent an XP image to a dozen new machines, 2 BSOD both times and the rest were fine so I called up the supplier and had an engineer on site next day......it was just the sata mode! Embarising for me but its a mistake I wont make twice and I did have to ask why was the BIOS set different on these 2 of the same batch/order number? 1
ToyHeartsFan Posted January 30, 2012 Posted January 30, 2012 Hardware faults can sometimes show up during an install even though XP was working ok before I'm afraid it doesn't mean much! I would also think about running hdd diags if mem diags pass ok. You could also use one of the free disk tools to wipe the drive so you know there isn't any junk left on there from the old installs. Is your copy of XP upto date i.e. with the SP3 on it? Don't you need at least SP2 for drives over 137GB? 1
Arcath Posted January 30, 2012 Posted January 30, 2012 If its a HP changing the SATA mode in the BIOS is needed to install XP. They had some random SATA controller which needed a driver, if you swap it to IDE mode its fine. Had this with one of the models of laptop, they've upgraded to 7 no probs but they need the change (or a hp xp disk) to install XP 1
X-13 Posted January 30, 2012 Author Posted January 30, 2012 that's no comma, that's a fully operational battle-apostrophe! ..and no, it's not needed A battle apostrophe, you say? Well then, I make it war-o'clock. RELEASE THE EMOTE-ZOMBIES!! ( ¬x_x)¬ {RAWR!) ( ¬x_x)¬ {RAWR!) ( ¬x_x)¬ {RAWR!)
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now