Posted on 2004-08-28
Medium Priority
Last Modified: 2010-04-19
0S= Win2K3 Datacenter Edition

Have OS on D: and formatted larger C: with Paragon Drive Backup Personal so OS can later be copied there but upon reboot after applying settings I get a PXE or similar screen which results in a message saying check cable + error code.

I previously had Longhorn 4074 installed on the C: and it had previously continued to go to the dual boot screen even though I deleted almost everything from the drive and removed the line from the boot record on the D:.

I've tried the fixboot and fixmbr commands from the recovery console on the OS setup disk to no avail - may I have made it worse?

What can I do to fix my bootup?
Question by:Serotonin_X_Infinite
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 12

Accepted Solution

ColinRoyds earned 2000 total points
ID: 11923430
try do a new installation but into a differnet folder on d: this should sort out the c: info that you are missing then edit the boot.ini to point to the correct installation path.

Author Comment

ID: 11923779
Good idea. Not sure how to create & install into new folder.
If I did a clean install on the C: would that be affected by anything on the D:?
LVL 12

Assisted Solution

ColinRoyds earned 2000 total points
ID: 11924008
when you do a new install, specify d: as the install path and it will say there is already an OS there do you want to install to a new directory and if so what is the path and use d:\winnt1 or such like.

Author Comment

ID: 11925296
LVL 12

Expert Comment

ID: 11925310
glad its sorted.

Featured Post

10 Questions to Ask when Buying Backup Software

Choosing the right backup solution for your organization can be a daunting task. To make the selection process easier, ask solution providers these 10 key questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question