640x480 Video Mode Download For Windows 11

[Shawnna Franz]

Itried to set the virtual desktop size to 800x600 in the bottle settings for steam and restarted steam.

Now everything is in that little nice window, have Greed Corp also with 800x600, but both apps in that virtual window.

I also thought about only setting the installed games to that resolution, editing the cxmenu desktop data and attaching the "-s " but - the possibility to edit the arguments for the menu entries doesn't seem to exist in the menu editor?

Doing it manually with the favorite editor should work but that isn't really "integrated"...

QUESTION: Which launch options do I have in Steam?

Advanced users can use the Launch Options of Steam to start the game in a specific resolution or to turn on/off fullscreen mode manually. In order to do this, right-click Greed Corp in the Steam Library, select "Properties", and then select "Set Launch Options". Now use the following commands to set the resolution and fullscreen mode:

I thought so, because steam itself works correct. But i wasn't sure where i should post the question to, to greed corp or to the steam forum because i think it's more a "how to hack how steam starts apps"... More below.

I tried that exactly, but it just starts with 640x480 again. If i enter another wine virtual desktop resolution it is working.

My hardware is capable of 1920x1080 but wine doesn't think it is.

Hm ok when i think about it, it seems that it is not a steam or greed corp issue, instead it seems to be a cxgames wine issue?

How does steam spawns applications within wine? Can parameters be "injected" to the wine call only for the spawned applications on start? e.g. give -s 1280x1024 to the wine call (even if wine is not called directly i think)?

I posted here to find a hack for the way how steam launches the games out of the library and to inject the wine -s parameters, and that is a steam issue - or to find a way to create start menu/desktop starters which the special wine parameters to launch e.g. greed corp.

Typically speaking when you launch Steam, the wine process is passed the video/screenmodes

available to it via the system video driver. In OSX, that would be the same modes displayed in

System Prefs -> Display ; in linux, it will be whatever the monitor EDID reported to the xdriver

at init , or, whatever else you have in the xserver configuration file. Some linux distros can

get this 'wrong' in a sense ...ie; technically speaking, a 4:3 aspect 1024x768 resolution screen

is invalid for a 16:10 aspect widescreen monitor, however, many newer monitors have their own

onboard 'smarts' that let them do that mode anyhow -- not all xserver setups are aware of this.

Right - when I saw your previous post and saw the resolution quoted, I figured you

either had a very interesting monitor, or you had a dual-head setup -- it wasn't

immediately obvious =) The issues with Wine and dual monitors has been known for some

time, and as I understand it, this is more mooted in the way the xserver/video drivers

present the situation (to the app), compared to how the win32 counterparts do the same

thing. Even putting wine/crossover aside for a moment, dual-head setups in linux can

be fickle even with native apps.....

....what ahem 'should' work, would be a scenario of say two, 1650x1080 displays, which would appear

as the composite $display area of 3300x1080 and would be addressed as localhost:0 , the left display

as localhost:0.0 and the right display as localhost:0.1 ...but it doesn't work that way. It might not

even be what you want to do, it's just an example. If one wanted to span -both- displays with the app's

video output, then you're still limited to whatever maximum resolution the win32 app is going to support.

If, say, that resolution was 1920x1080 maximum, the 'proper' way to display that on the composite desktop,

would be with the 1920x1080 viewport centered on the two display areas, with a 690pixel wide black bar

to the left/right of that. If you did that, then you have to calculate mouse coordinates and so forth,

from a 0,0 position that appears at 690 of the overall display size, and things get uglier from here on in...

Like I say though, it depends on exactly what you're trying to do. What one would -like- to have happen,

is if the app's max resolution was 1920x1080, being able to present that as 2 viewports each of 960x1080

in size might work (supposing the display handled whatever modeline that calculates out to)..ie; you change

the maximum $display size presented by the 2 monitors. This has problems as well...

It really depends on the app tho' ...ie; if Greed Corp supported 3300x1080 in the example above, it'd likely

all work fine, but as that isn't the case, one wishes you could command the GPU on the video card to just

retarget the graphics steams for you ...

BUT i deeply remember in my brain that since the last years i did several fights with Xinerama and twinview due such facts like 1024x768 in the middle of both monitors (really useful configuration...) with just black borders around and such stuff. Exactly what you wrote. The current problem is just 1440x900 on the left side and 1920x1200 on the right side - that also hurts my gnome desktop a lot because some icons and apps are just "stupid". The "awesome windows navigator" have big problems with calculating it's correct position...

What i have never understood is that someone can think about using several monitors as "one big" monitor in just normal office or home use. That is not true, there are no borderless home monitors,

Point.

I remember some setting that worked with nvidia and behaved like on windows (not using some ati driver stuff which does the same trash maximizing on both monitors). I think it was Xinerama with xorg and two-screen setup.That worked as it should - BUT - if i remember correct - that killed the 3d acceleration.

That is a looooong time ago (3 or 4 years when i tried several setups), i thought the problems were fixed in xorg and the drivers sigh...

Nevermind, that's just history. I'll do the same xinerama-twinview tests again.

I've got about 50 users who successfully use LogMeIn to work from home with no issues. Just this week, one user started experiencing a problem where when he logs into his computer, one of his two monitors is set to 640x480. He's usually able to go into the Windows display settings and change the second monitor back to 1920x1080. On at least one occasion, he was not able to change the resolution.

The host application was a few versions out of date, so I uninstalled and reinstalled it along with any recent windows updates for 20H2, but this didn't help. Unfortunately I don't have any influence over his home setup, though the user tells me that he installed all pending Windows updates and restarted since this first happened.

I sat at his desk in the office while he logged in from home and observed the monitor switch to 640x480 resolution as he connected. It seems like it's an issue on the host computer, but I'm not sure what to do about it. I turned off the display accelerator just to see if that had anything to do with it. Any other ideas?

HP Pavlion p7-1247c. I am stuck at 640x480. I can get to the change resolution setting but the display setting is grayed out so I am stuck at 640x480. I can boot to safe mode and I can change the resolution while in safe mode but not when I boot normally. I tried a system restore back to how it was first shipped to me. I can't complete the initial setup because I am at 640x480 and I can't see or click on the button to continue because it is off the screen. I found that there is a boot option for low resolution which is where I seem to be stuck. I can't find any way to turn off the boot to low resolution. Also, it seems that the initial setup program assumes a wide aspect ration monitor. This does not work with my old monitor which will do 1280x1024, but is stuck at 640x480.

I think the real reason that I tried swapping the cable is that the last tech support guy said that it would not be the cable. This is just proof that sometimes it is the most simple part of the whole system which can cause the most difficulty.

Here is the driver for the integrated video and a guide to help you install it in Safe Mode. I used a third party source to identify the integrated video included in the A8 3820 processor. If the link is incorrect, you can use the same page to indentify the appropriate driver. Once the appropriate driver is installed it may solve your problem.

Thanks for the link to the driver. I assumed that the driver from HP would work on an HP computer, it didn't. I have the problem computer packed up and ready to ship back to HP. After spending some quality time with HP support they decided that the video card is bad and they want me to send the computer back to them so that they can repair it.

Well, I got my computer back from HP today. The note included with it said that the mother board was replaced. I guess they replaced the motherboard because they thought there was a problem with the video circuit on it. I hooked it up and foudn that nothing had changed! I am still stuck at 640x480 unless I boot to safe mode. In safe mode it boots to 800x600 and I can change it to what ever I want it to be. Well, at least to the supported resolutions.

I booted normally and then installed the AMD driver which was suggested. Nothing happened, I'm still stuck at 640x480. The installation was challenging because the install program assumed I was running at a higher resolution. I had to hit 'tab' a couple of times and then'enter' and luckily I happened to be on the 'next' button and was able to continue with the installation. It was a waste of time because it didn't work for me.

I included a two page report when I sent the compter back. I carefully explained what the problem is and what I had done to correct the issue. This seems to be another waste of time because it seems that no one bothered to read it.

3a8082e126