|
|
|
|
#1
07-21-2009, 00:10
|
|||
|
|||
|
may be the driver studio has the higher priority than the vmware drivers, so some function may be blocked by the debugger as the system boots.
|
|
#2
07-21-2009, 08:51
|
||||
|
||||
|
Quote:
a network monitor a dhcp monitor a driver to load, run, and edit the VMs But I am strictly speaking from a Windows PoV Linux has never been my forte
__________________
Even as darkness envelops and consumes us, wrapping around our personal worlds like the hand that grips around our necks and suffocates us, we must realize that life really is beautiful and the shadows of despair will scurry away like the fleeting roaches before the light.
|
|
#3
09-20-2009, 09:25
|
|||
|
|||
|
I've encountered the same issue once. It was resolved by using a linux boot disk and re-installing lilo. I think in your case (Fedora) uses Grub as the linux loader.
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| olly & app crash | optimus_prime | General Discussion | 11 | 06-10-2006 00:03 |
| Visual Studio .Net installation help | Nilrem | General Discussion | 15 | 03-11-2004 06:55 |
Hybrid Mode
