VirtualBox

Ticket #10140 (new defect)

Opened 2 years ago

Last modified 2 years ago

Samsung CLP 320 series driver installation crashes WinXP guest

Reported by: RJVB Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.8 Keywords:
Cc: Guest type: Windows
Host type: Mac OS X

Description (last modified by frank) (diff)

Installation of the specific drivers for my Samsung CLP 325W printer fails, causing a crash that provokes an instant reboot somewhere during the "System update" phase towards the end of the installation.

Affected drivers: 3.11.34.00:18, see  here. guest OS: MS Windows XP SP3 (32bit)

Procedure: launch the installer linked to above; after the unarchiving step, click on "Install now" (not on the network option below). Chose the option without search for an available printer, and sit back. On my machine the install proceeds normally, until it arrives to the "System update" stage, where it will either provoke a reboot of the guest, or else lock it up (with screen corruption). This happens with Virtual Box 4.1.8 with the matching guest additions, and reminds me of a similar phenomenon I had with I think 4.1.4 while simply writing specific bytes to a text file on a host share. The universal driver (v 2.02.05.00:25) installs OK but appears not to find my printer (or fails to communicate with it).

Attachments

VBox.log.1 Download (112.3 KB) - added by RJVB 2 years ago.

Change History

Changed 2 years ago by RJVB

comment:1 Changed 2 years ago by frank

  • Priority changed from blocker to major
  • Description modified (diff)

This instant guest reboot is surely annoying but certainly not a blocker. It affects only certain guests.

When the guest reboots, could it be a blue screen which forces an immediate reboot? In that case, the behavior for Windows blue screens can be configured.

comment:2 Changed 2 years ago by RJVB

Well, it does block something: since the installation is never finished, the driver isn't installed properly, and cannot be used. I cannot of course test other MS Windows guests, but it's evident that Linux and Solaris guests aren't affected...

There is no blue screen, the reboot is due to what looks like a hard reset/power cycle. In other words, one moment you have your guest running doing the installation, the next moment you have the VB bootup window.

comment:3 Changed 2 years ago by frank

With certain guests I don't refer to Windows guests in general. The reboot is apparently triggered because you install a special driver in the guest. That would be a bug (if the same does not happen on real hardware!) but that would only affect users of that specific driver.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use