Warning: VISTA-SP1 and WinSP:WW2/MBT problems!

[TheDesertFox]

Hi,

no, with Ultimate you are allowed to use the same licence on your native and your VPC. With Enterprise you are allowed to use up to four VPCs with the same licence on one machine.

In fact the VPC on my Vista64 rig is the same licence as my notebook.

I dunno about Home Premium, but anyways you can install XP as a VPC on that machine (if you have a licence handy).

To change VRAM from the default setting to the max of 16megs you can edit the *.vmc file and adapt these lines:

<video_adapter>
<vram_size type="integer">128</vram_size>
</video_adapter>

That will give you 16megs of VRAM, which isn´t necessary for WinSP but might be handy for other apps.

cheers

[Wdll]

Thank you.

BTW, aren't the requirements of winspmbt 32MB of video ram?

[TheDesertFox]

Hi,

yes 32megs is what the gameguide recommends. However it runs flawless in 1280x1024 on my VPC.

cheers

[Horses]

Hi,

thanks for your help and support.

Both WinSP:WW2/MBT are running fine and smooth now in windowed mode. The problem was the font size (it was too large). I adjusted it to standard settings 96DPI and now all is ok.

@TheDesertFox
I use the older 8800GTS G80 with 320MB with Asus Mainboard (P35-chipset).

[Mobhack]

Horses said:
Hi,

thanks for your help and support.

Both WinSP:WW2/MBT are running fine and smooth now in windowed mode. The problem was the font size (it was too large). I adjusted it to standard settings 96DPI and now all is ok.

@TheDesertFox
I use the older 8800GTS G80 with 320MB with Asus Mainboard (P35-chipset).

I now recall someone had a problem with Mobhack, way back in the Windows 98 days (before I needed reading glasses!), and it eventually turned out that he had reset his windows to use large fonts.

Changing any version of Windows away from the default 96DPI is never a good idea, as it can thoroughly mess up any dialogue boxes, buttons, display of images etc - the size of the dialogue box or text button or image box X-Y pixels is fixed to whatever was used in the form designer and won't rescale, but any now-larger text (or image, if it rescales them - been a long while since I looked at the problem) then tries to squash into the existing pixel area and simply makes a mess. Therefore highly not recommended!.

In the old CRT days - the best way to make Windows larger for poor eyesight etc (without pulling one's reading glasses out! ) was to simply use a smaller window size on your monitor (e.g. 800 by 600 instead of say 1024 by 768). The "feature" to change windows DPI seems really never to have been a usable one due to side-effects, and it seems Vista continues that tradition!. Nowadays, with LCD screens, using a non-native resolution can result in "fuzzy" screens, one reason I still have the 10-ton (or so it seems if I shift it!) 19 inch CRT gathering dust in the spare bedroom. It's the only way I can test the game at maximum resolution now, as my LCD 1280 by 1024 monitor simply cannot handle that resolution, though the graphic card will - and will happily let me try it on the LCD monitor, but with a blank screen as a result. The monitor hardware seems not to tell the GFX card it can't hack the resolution, and so Windows believes the GFX card it seems. (The CRT was also better at colour handling - my desktop used to be the "autumn" one with the trees and leaves etc, but the new LCD screen seems somewhat washed-out & faded with browns and so I tend to use a blueish one instead now).

Cheers
Andy

[Wdll]

Mobhack sounds like you need to buy a new larger TFT monitor.

[Wdll]

btw, new pc, Vista 64, quad core 9550, radeon 4870X2, and they run the game just fine, though just in case I have the intro disabled.
My only wish is, for something I will post elsewhere lol.

[DRG]

Try it with the intro on once and see what happens

Don

[Wdll]

Originally Posted by DRG

Try it with the intro on once and see what happens

Don

crashes.

Problem signature:
Problem Event Name: APPCRASH
Application Name: winspmbt.exe
Application Version: 1.0.3.5
Application Timestamp: 00000000
Fault Module Name: quartz.dll
Fault Module Version: 6.6.6001.18063
Fault Module Timestamp: 4812e26d
Exception Code: c0000090
Exception Offset: 00099b22
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 5fba
Additional Information 2: b3e1f2122844d4e8d212ddae5bccb695
Additional Information 3: 6874
Additional Information 4: 42f60de55b5ca326eb05bdf47880f16c

[Mobhack]

Originally Posted by Wdll

crashes.

Problem signature:
Problem Event Name: APPCRASH
Application Name: winspmbt.exe
Application Version: 1.0.3.5
Application Timestamp: 00000000
Fault Module Name: quartz.dll
Fault Module Version: 6.6.6001.18063
Fault Module Timestamp: 4812e26d
Exception Code: c0000090
Exception Offset: 00099b22
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 5fba
Additional Information 2: b3e1f2122844d4e8d212ddae5bccb695
Additional Information 3: 6874
Additional Information 4: 42f60de55b5ca326eb05bdf47880f16c

quartz.dll (a part of Microsoft's own directshow it seems) has problems in Vista.

Try googling on "quartz.dll vista"


Cheers
Andy