iohr Posted April 4, 2011 Posted April 4, 2011 I am having trouble "building" an RM CC4 Classroom computer in a VMWare Workstation 7 Virtual Machine. The Build CD ISO boots correctly and allows me to fill in the necessary details: *username *password then: Computer Name etc. But after it "Applies OS Image" and reboots, it Bluescreens with a STOP: 0x0000007B error message. It seems, from my searches around VMware forums to be related to the disk controller drivers. I don't get this problem with VMWare ESXi, just VMWare Workstation. I'm going to have a look at the configuration files for both, to see which disk controller they use.
synaesthesia Posted April 4, 2011 Posted April 4, 2011 Go into the virtual machines BIOS and change the hdd type to legacy/ide/compatible or whatever it was called. Think that only occurs for XP images though, not so much Vista/7.
iohr Posted April 4, 2011 Author Posted April 4, 2011 There is no option for that in a VMWare Workstation 7.1 VM BIOS. Do you know if it can be changed in the .vmx file?
cpjitservices Posted April 4, 2011 Posted April 4, 2011 can you clean install a version of 7 and then run the SmartClient and build it like that ? Sorry never used CC4 - my experience really is CC2 & 3
russdev Posted April 4, 2011 Posted April 4, 2011 Like others posts had that with virtualbox and changing to IDE I am sure fixed it. As said smartclient maybe way to go... Russ
Arthur Posted April 4, 2011 Posted April 4, 2011 Which OS are you using? The disk controller is determined by which one you select when you are creating a new virtual machine or when you go to add a new virtual disk in the Add Hardware Wizard. http://i.min.us/ik9AM8.png http://i.min.us/ik5u68.png http://i.min.us/ik5sy0.png
bossman Posted April 4, 2011 Posted April 4, 2011 (edited) Try the nic settings instead of NAT use bridged, had this problem with virtualbox and this solved it. Also the above settings also given in the choice of HDD controller should also be changed. Edited April 4, 2011 by bossman
cpjitservices Posted April 4, 2011 Posted April 4, 2011 If that doesn't work - Smartclient will do the trick...............
Chris_ Posted April 4, 2011 Posted April 4, 2011 Not sure if it's related but I was having troubles building a CC4 workstation on an ESXi server. Managed to get it to work in the end by setting the Operating System type as Windows Vista in the VM settings.. Something to do with the Win PE version that the CC4 build client uses?
PiqueABoo Posted April 4, 2011 Posted April 4, 2011 I've seen that with an earlier VMW: Assuming it's the same issue, make sure the VM is configured to use IDE disks as in Arthur's screen-shots and then get rid of any references to SCSI devices in in the *.VMX file, because at least one version of VMW still added a SCSI adapter even though you'd selected an IDE disk. Open the *.VMX file in an editor and look for lines like: scsi0:0.present=true, and if you find any change the "true" to "false (or just try deleting those lines entirely - I have no references to SCSI in the VMX file I use for XP VMs).
iohr Posted April 5, 2011 Author Posted April 5, 2011 Thanks for all your work guys. I had opened a support call with RM too. They posted me back a known good .vmx file that they use with VMWare Workstation for CC4 Builds. I will try and attach. They are of the same opinion, that it requires you to ensure there is no reference to a SCSI disk controller anywhere in the .vmx file. I think that is the problem. I had to add .txt because of the file extension restrictions. If you need to use this, please strip it off and add .vmxCC4 SR2 PBuild_dot_vmx.txt
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now