I do not understand this post at all. Is this just some rambling of you playing around with DosBox or does it have a point somewhere within?

I'd like to know about that too.
DOSBox has been working fine on Vista for me; I haven't done much with it, but window, full screen, text, graphics, sound (PC speaker), keyboard and mouse are all fine.

It was working fine for me even back with RC1.

Dosbox is a blast on Windows Vista. I get amazing speed, stability, and compatibility. 😁

He sent me a message and said it was about an issue with Tomb Raider that he found a fix for (GliDOS patch). I think this is a good opportunity to remind people to be specific with their posts and politely request they not make frivolous posts and especially not frivolously creat threads (unless the forum is for that, like Milliways and the "off-topic" or "miscellaneous" forums on some sites).

I recently had to get PADS Perform DOS v6.0.1 working in a new notebook computer. It is an HP Pavilion dv9429 which has an AMD Turion 64 X2 TL-64, 2GB DDR2, and Windows Vista Home Premium. I have a desktop PC with Win XP SP2 with DOSBox, PADS Perform, and PortTalk already working.

Basically all I did was copy the C:\PADS directory and my C:\Programs directory (which has the DOSBox and PortTalk directories) to the notebook's C: drive. Then I copied my Desktop Shortcut to start DOSBox / PADS Perform to the notebook desktop. I installed PortTalk as detailed before; copying porttalk.sys to the C:\WINDOWS\system32\drivers directory, double clicking porttalk.reg to install in the registry, and rebooting.

PADS Perform worked the first time. I didn't have to change anything. So DOSBox and PADS Perform DOS work fine in Windows Vista. The performance was very good.