Durons and Norton Ghost
Results 1 to 5 of 5

Thread: Durons and Norton Ghost

  1. #1
    Registered User
    Join Date
    Mar 2001
    Location
    Dorset, UK
    Posts
    103

    Post Durons and Norton Ghost

    I use Norton Ghost at my place of work to aid PC roll out and have several basic images that I use. However we have just gotten in 2 Duron 850's and I cant get the Windows 2000 basic image to work. I have been told that with windows 2000 I would need to start from scratch because it is a Duron and not an Intel (What the image was made with). Is this true?

  2. #2
    Darren Wilson
    Guest

    Post

    You are probably right there, as the Intel board is most probably using different Chipset drivers to the Duron. I gather you are getting the 'Inaccessible_Boot_Device' upon bootup?

  3. #3
    Registered User Cave_Dweller's Avatar
    Join Date
    Mar 2001
    Location
    Pennsylvania
    Posts
    355

    Post

    We used to have one "Generic" image that worked on just about everything. Before creating the image, we would boot into safe mode and delete the Enum key. The first time a machine was booted up, the add new hardware wizzard would run and after a couple reboots all was fine.

    The newer mother boards don't work well with these "Generic" images and we have started creating MB specific images. Instead of deleting the Enum key on new images, I remove items that may be different from one machine to another, such as the monitor, video card, Nic, etc...
    Never argue with an idiot. They drag you down to their level, then beat you with experience

  4. #4
    CobraTekMax
    Guest

    Post

    Yep, Darren's right (as usual ). Win2K doesn't like being run from a different type of hard drive controller than what it was originally installed on.

  5. #5
    Darren Wilson
    Guest

    Post

    Originally posted by MIFUIC:
    We used to have one "Generic" image that worked on just about everything. Before creating the image, we would boot into safe mode and delete the Enum key. The first time a machine was booted up, the add new hardware wizzard would run and after a couple reboots all was fine.

    The newer mother boards don't work well with these "Generic" images and we have started creating MB specific images. Instead of deleting the Enum key on new images, I remove items that may be different from one machine to another, such as the monitor, video card, Nic, etc...
    Only drawback to the ENUM fix, is that it does not work with Win2K.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •