Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Please play nicely.  No one wants to listen/read a keyboard warriors rants....

Pages: 1 [2]  All   Go Down

Author Topic: Quick PC Problem....  (Read 3096 times)

0 Members and 1 Guest are viewing this topic.

M16

  • Intermediate Member
  • ***
  • Offline Offline
  • Gender: Male
  • Lancs
  • Posts: 319
    • View Profile
Re: Quick PC Problem....
« Reply #15 on: 02 April 2008, 23:23:45 »

Also shown here (see method 2)
http://support.microsoft.com/kb/318728
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107038
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Quick PC Problem....
« Reply #16 on: 02 April 2008, 23:25:14 »

Quote
Had the same problem few weeks ago. believe me it works. Also this is the solution as published in the MCP 70-720 examination guide.
If you oot from the XP disk as you would when you do a fresh install if there is already a version on the harddrive it will give you a repair option.
Yup, fully aware of the repair processes. Should be after working with NT since 3.5, and using it since the initial 3.1 ;)

I would suggest if that fixed it, then a user with admin rights had deleted them.

Oh, and don't pay too much attention to the knowledge you gained to pass your MCP - MS training (except the infrastructure design courses) and reality are miles apart (hence why when I sit in on recruiting interviews, I pay no regard to MCSE).
Logged
Grumpy old man

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107038
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Quick PC Problem....
« Reply #17 on: 02 April 2008, 23:27:16 »

Quote
Also shown here (see method 2)
http://support.microsoft.com/kb/318728
Which confirms what I said - boot.ini. ntdlr missing is aways a fault in boot.ini. Esp if you read the circumstances of the OP moving the HDD between machines. It will be the boot.ini

Oh, and did I mention boot.ini? Coz it will be the rather boot.ini!
Logged
Grumpy old man

M16

  • Intermediate Member
  • ***
  • Offline Offline
  • Gender: Male
  • Lancs
  • Posts: 319
    • View Profile
Re: Quick PC Problem....
« Reply #18 on: 02 April 2008, 23:29:37 »

I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
Logged

Vamps

  • Offline Offline
  • Gender: Male
  • Bishop Middleham, Co Durham.
  • Posts: 24708
  • Flying Tonight, so Be Prepared.
    • Mig 2.6CDX and 2.2 Honda
    • View Profile
Re: Quick PC Problem....
« Reply #19 on: 02 April 2008, 23:34:04 »

Hope they ask you how not to do a link.!!!!!!!!!!!!!!!1 :(
Logged

M16

  • Intermediate Member
  • ***
  • Offline Offline
  • Gender: Male
  • Lancs
  • Posts: 319
    • View Profile
Re: Quick PC Problem....
« Reply #20 on: 02 April 2008, 23:35:03 »

Quote
Hope they ask you how not to do a link.!!!!!!!!!!!!!!!1 :(
Funny  ;D
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107038
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Quick PC Problem....
« Reply #21 on: 02 April 2008, 23:44:27 »

Quote
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid.  Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.

Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.

Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation).  Just the AD part to worry about.  IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.

Good luck with exam :)
Logged
Grumpy old man

Vamps

  • Offline Offline
  • Gender: Male
  • Bishop Middleham, Co Durham.
  • Posts: 24708
  • Flying Tonight, so Be Prepared.
    • Mig 2.6CDX and 2.2 Honda
    • View Profile
Re: Quick PC Problem....
« Reply #22 on: 02 April 2008, 23:47:45 »

To be honest guys I have no idea what you are talking about  :-[ Sounds very impresive though.  ;D ;D ;D
Logged

M16

  • Intermediate Member
  • ***
  • Offline Offline
  • Gender: Male
  • Lancs
  • Posts: 319
    • View Profile
Re: Quick PC Problem....
« Reply #23 on: 02 April 2008, 23:52:49 »

Cheers for that. Have just rebooked 70-290 (windows server 2003) after failing by 2% so gonna have another crack at that then onto windows server 2003 Network Infrastructure.
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107038
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Quick PC Problem....
« Reply #24 on: 02 April 2008, 23:54:53 »

Quote
Cheers for that. Have just rebooked 70-290 (windows server 2003) after failing by 2% so gonna have another crack at that then onto windows server 2003 Network Infrastructure.
Ah, thats not good.

Its been a while, but IIRC, Server MCP covers Server and XP Pro? Which bit were your week on?
Logged
Grumpy old man

Entwood

  • Omega Queen
  • *****
  • Offline Offline
  • Gender: Male
  • North Wiltshire
  • Posts: 19566
  • My Old 3.2 V6 Elite (LPG)
    • Audi A6 Allroad 3.0 DTI
    • View Profile
Re: Quick PC Problem....
« Reply #25 on: 02 April 2008, 23:56:14 »

Quote
Quote
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid.  Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.

Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.

Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation).  Just the AD part to worry about.  IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.

Good luck with exam :)
Totally agree, however a "fix" that sometimes works - about 75% - is to boot to the windows CD, work to the install screen where it says it has found a previous windows install, the choose "R" for "repair install" [note : this is different to the repair consol screen that goes to  DOS]

Windows will delete and reinstall many files from this point on AND rewrite boot.ini .. it works very well most of the time. Takes about 40 minutes. Then install the drivers for the new motherboard etc etc

as I said .. not gauranteed but about a 75% success rate, and keeps all loaded programs intact  .. :)
« Last Edit: 02 April 2008, 23:57:15 by entwood »
Logged

M16

  • Intermediate Member
  • ***
  • Offline Offline
  • Gender: Male
  • Lancs
  • Posts: 319
    • View Profile
Re: Quick PC Problem....
« Reply #26 on: 03 April 2008, 00:03:40 »

Had a few problems with Terminal Security Services
Logged

LouisCorney

  • Guest
Re: Quick PC Problem....
« Reply #27 on: 03 April 2008, 01:06:27 »

Quote
Good luck, but swap the dvd drive over with CD, and build XP on the PC that the HDD belongs to is best option ;)

This sorted it, and some other niggling problems  :y
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107038
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Quick PC Problem....
« Reply #28 on: 03 April 2008, 19:33:02 »

Quote
Quote
Quote
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid.  Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.

Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.

Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation).  Just the AD part to worry about.  IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.

Good luck with exam :)
Totally agree, however a "fix" that sometimes works - about 75% - is to boot to the windows CD, work to the install screen where it says it has found a previous windows install, the choose "R" for "repair install" [note : this is different to the repair consol screen that goes to  DOS]

Windows will delete and reinstall many files from this point on AND rewrite boot.ini .. it works very well most of the time. Takes about 40 minutes. Then install the drivers for the new motherboard etc etc

as I said .. not gauranteed but about a 75% success rate, and keeps all loaded programs intact  .. :)
And quicker to rebuild from scratch ;)
Logged
Grumpy old man
Pages: 1 [2]  All   Go Up
 

Page created in 0.025 seconds with 16 queries.