Installation of DriverStudio 3.2 causes System Crash

[rcer]

Yesterday I installed Driverstudio 3.2 on a Linux host system, running VMWare 6.5. with WinXP as guest system.

The initial installation went flawless, with SoftIce running smoothly under Xp.
However after playing around for an hour I shut down the guest & host system, and now Linux refuses to boot. Instead of Fedoras friendly blue log on screen
I am now getting a screen which flashes back and forward between pitch black and bright white.
has anybody experienced a similar problem before?

Any advice with suggestions as how to fix this are welcome

Regards.

[jonwil]

I don't see how anything you installed on your VMWare install could affect your Linux host.

[UNIX]

Did you install vmware also at that time or at an earlier time? Maybe you made something wrong while installing vmware - otherwise i agree with jonwill, that changes you make on a vm won't affect your host system.

[memo-5]

I am sure that it has no thing to do with the DriverStudio installation on VMware
I did installed Driverstudio on VMWare running Linux before and I did not face any issue.

[rcer]

I installed VMware about 3 months ago and never had a problem.

Anyway, maybe it was just a coincidence that Linux crashed after I installed Driverstudio 3.2


I tried the last couple of days to restore the system without wiping the hard drive, but eventually got so frustrated that I am now doing a clean install

regards

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.

[D-Jester]

Originally Posted by FlyingSnow

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.

As far as I know, VMWare only installs 3 drivers on the host system:
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

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.