tcengineer
asked on
How to bypass a Symantec Ghost create image task sent to a windows vista client?
Using Symantec Ghost Solution Suite 2.0, I remotely installed the client on a windows vista machine. I created a "Create Image Task" pointed at the vista machine. The PC reboots but gets stuck with the following message:
-------------------------- ---------- ---------- ---------- -
NVIDIA DOS BDIS Ethernet Driver (V220.0527)
Copyright (C) 2001-2005 NVIDIA Corporation
Copyright (C) 1997-2000 Intel Corporation
IBM Protocol Manager Version 2.1
MAC/DIS to Packet Driver converter loaded. Version 1.19
Copyright 1992 FTP Software, Inc. All rights reserved.
Portions Copyright(c) 2000-2004 Symantec Corporation
Intel Universal NDIS Driver, PXE-2.0 (build 082)
Copyright (C) 1997,1998,1999 Intel Corporation
NVIDIA DOS NDIS Ethernet Driver already loaded!
NVIDIA DOS NDIS Ethernet Driver (V229.0527)
Copyright (C) 2001-2005 NVIDIA Corporation
Copyright (C) 1997-2000 Intel Corporation
PXE-E6A: Invalid UNDI State
-------------------------- ---------- ---------- ---------- -
How do I bypass this so I can boot the PC?
I'm desperate!
Thanx!
John 88{Q
--------------------------
NVIDIA DOS BDIS Ethernet Driver (V220.0527)
Copyright (C) 2001-2005 NVIDIA Corporation
Copyright (C) 1997-2000 Intel Corporation
IBM Protocol Manager Version 2.1
MAC/DIS to Packet Driver converter loaded. Version 1.19
Copyright 1992 FTP Software, Inc. All rights reserved.
Portions Copyright(c) 2000-2004 Symantec Corporation
Intel Universal NDIS Driver, PXE-2.0 (build 082)
Copyright (C) 1997,1998,1999 Intel Corporation
NVIDIA DOS NDIS Ethernet Driver already loaded!
NVIDIA DOS NDIS Ethernet Driver (V229.0527)
Copyright (C) 2001-2005 NVIDIA Corporation
Copyright (C) 1997-2000 Intel Corporation
PXE-E6A: Invalid UNDI State
--------------------------
How do I bypass this so I can boot the PC?
I'm desperate!
Thanx!
John 88{Q
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You, my friend, are a GAWD!
It was F8. This allowed me to walk past the network drivers to the C:\ghost directory. Inside there, is a command called ghreboot which reboots to Windows.
Once I did that, I rebooted again to confirm it continues to boot into Windows, which it does!
Thank you Thank you Thank you!!!!
John 88{Q
It was F8. This allowed me to walk past the network drivers to the C:\ghost directory. Inside there, is a command called ghreboot which reboots to Windows.
Once I did that, I rebooted again to confirm it continues to boot into Windows, which it does!
Thank you Thank you Thank you!!!!
John 88{Q
You're very welcome...glad I could help. :)
ASKER
It was F8. This allowed me to walk past the network drivers to the C:\ghost directory. Inside there, is a command called ghreboot which reboots to Windows.
Once I did that, I rebooted again to confirm it continues to boot into Windows, which it does!
Thank you Thank you Thank you!!!!
John 88{Q