[piper28]

Ok, I'm testing my unattended installs in vmware, but one issue I've run into is kinda annoying. Regardless of what I do it seems to come up in 640x480 mode, wanting to change the resolution later. This causes me problems in two places. One is I have an app that likes to complain if the resolutions isn't at least 800x600 on install (yet it still installs after hitting ok), and I'd also like to consider using WPI, which doesn't appear to be happy with 640x480. I've tried setting higher resolutions in winnt.sif, and I've also tried adding the display driver with the oem driver path stuff, but nothing seems to make it come up in anything other than 640x480. Since a fair number of people seem to use vmware to test, I'm hoping that maybe someone has come up with a solution for this and can point me the right way.

(VMWare 5, XP SP2 unattended install)

Thanks.

[Kelsenellenelvian]

Sorry That is just how it works with vmware.

[Shark007]

Quote

I've tried setting higher resolutions in winnt.sif,
and I've also tried adding the display driver with the oem driver path stuff.

I use vmwware and on 1st boot i have 1024x768 @ 32bit resolution just as its set in WINNT.SIF

Extracts from winnt.sif:

[Unattended]
UnattendMode=FullUnattended
UnattendSwitch=Yes
OemSkipEula=Yes
OemPreinstall=Yes
UnattendSwitch=Yes
OemPnPDriversPath="Drivers"

[GuiUnattended]
DetachedProgram=%systemdrive%\drivers.exe

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=85

comment - OemPnPDriversPath is populated @T-39 using a selfextracting file containing all my drivers placed on the CDrom in $OEM$\$1\drivers.exe - this is set to extract the drivers to %systemdrive%\drivers To further add to this, On real installations all my display/sound/printer etc. drivers are installed properly this way also. Just remember that OemPnPDriversPath must lead to the drivers INF file.

I've experienced problems when the OemPnPDriversPath actual paths gets to deep, so now i just lump all the drivers into a single folder called drivers. Luckily for me, none of my drivers have conflicting filenames.

shark

This post has been edited by Shark007: 21 December 2005 - 04:43 AM

[unbannable]

does not work

[Shark007]

unbannable, on Dec 21 2005, 07:10 AM, said:

does not work

I'm sorry it doesnt work for you. I've done litterally 100's of vmware installs, and i find the 1024x768 a bit annoying and turn it down to 800x600 on 1st boot. maybe if you explained yourself in depth, i might be able to assist you where you are going wrong.

shark

[Shark007]

Quote

unbannable wrote:
(muiz , banned thx to shark007 )

muiz, aka unbannable, QUIT the attacks, some people come here for real help.
Your public harrassment will only bring you shame. I didnt ban you. I am not a system operator on this board. If you were banned, it was caused by your own actions, not mine.

see this POST

piper28, if you require further assistance, you may contact me thru PM.

shark

This post has been edited by Shark007: 21 December 2005 - 06:22 PM

[Halfwalker]

piper28, on Dec 20 2005, 04:49 PM, said:

Ok, I'm testing my unattended installs in vmware, but one issue I've run into is kinda annoying. Regardless of what I do it seems to come up in 640x480 mode, wanting to change the resolution later. This causes me problems in two places. One is I have an app that likes to complain if the resolutions isn't at least 800x600 on install (yet it still installs after hitting ok), and I'd also like to consider using WPI, which doesn't appear to be happy with 640x480. I've tried setting higher resolutions in winnt.sif, and I've also tried adding the display driver with the oem driver path stuff, but nothing seems to make it come up in anything other than 640x480. Since a fair number of people seem to use vmware to test, I'm hoping that maybe someone has come up with a solution for this and can point me the right way.

(VMWare 5, XP SP2 unattended install)

Thanks.

Add this to your batch file that installs VMWare Tools ...

YOUR\PATH\TO\1365VidChng.exe 1024x768x32@85 -q

Google for 1365VidChng.exe - I don't recall where I got it. Syntax is easy, but you have to use 85Hz as the refresh rate in a VM once VMWareTools have been installed.

I actually use RogueSpear's method of a VBS script to see if we're in a VM, and only install VMWareTools then. The VBS code is like this :

Option Explicit
Dim ws, fs, colDrives, objDrive, strOEM
Set ws = WScript.CreateObject("WScript.Shell")
Set fs = CreateObject("Scripting.FileSystemObject")
Set colDrives = fs.Drives
For Each objDrive in colDrives
	If fs.FileExists(objDrive.DriveLetter & ":\WIN51") Then strOEM = objDrive.DriveLetter & ":\Apps\200.VMWareTools"
Next

Sub InstallVMtools
	Dim strComputer, objWMIService, colBIOS, objBIOS, i
	Dim strKey
	strComputer = "."
	strKey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\090\"
	Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
	Set colBIOS = objWMIService.ExecQuery("Select * from Win32_BIOS")
	For Each objBIOS In colBIOS
		If Not IsNull(objBIOS.SerialNumber) Then 
		   	If Left(objBIOS.SerialNumber(i),6) = "VMware" Then 
				ws.Run(strOEM & "\VMWareTools-v5.5.exe"),0,True
				ws.Run "c:\windows\system32\1365VidChng.exe 1024x768x32@85 -q",0,True
			Else
				ws.Run "c:\windows\system32\1365VidChng.exe 1024x768x32@60 -q",0,True
			End If
		End If
	Next
End Sub

InstallVMtools

If we're in a VM, install VMWareTools and set res to 1024x768 at 85Hz, otherwise set to 1024x768 at 60Hz. The VMWareTools install is called 2nd in my list of apps etc being installed.

Works like a charm.

D.

[trb48]

The reason that the resolution is so small is because VMWare uses a graphics driver that Windows does not natively support.

The way that I found around this same problem was to intergrate the VMWare drivers into my ISO. As you probably know, you can install vmware tools and you can do all kinds of cool stuff after it is installed. I found the VMWare tools ISO (it was in the VMWare program files directory) and I found all of the drivers. I then used nlite to intergrate them into my Windows ISO.

The only problem that I found is that during the installation process a "Found New Hardware Wizard" appears (for three different devices). As far as I can tell, you cannot silently install VMWare drivers. But after a few clicks you can have the resolution set it according to the winnt.sif specs. The resolution does not change until windows reboots (right before it runs the GuiRunOnce).

This method installs the correct driver, and then Windows can change the resolution like it is supposed to.