Does anyone know exactly how the resolution of the theme is picked on boot? I am working on customizing my own theme, but for testing purposes I pushed out the McAfee extended theme. For whatever reason, I always get the 1024x768 version of the theme.
-Using a widescreen laptop (Dell D620) and a standard screen laptop (Dell D610) both get the 1024x768 when booted undocked. I tried docking them with a 20' standard monitor and also with a 22' widescreen monitor and I still get the 1024x768.
-I checked the machine group properties, and the graphics mode was set to default. I tried setting that to force a different resolution, synchronized the laptop, and it still chose 1024x768.
-The graphics.ini file has all the resolutions listed (and Im assuming its correct, since its the unmodified McAfee one) and all the correct resolution subfolders are being copied down to the machines correctly
-I have also replicated this same behavior with the custom theme I am working on. Cant get it to choose anything other than 1024x768.
At this point Im not sure I know what else to check or try. I have a feeling that I simply have a misunderstanding of how that resolution is choosen on boot. Anyone have any insight for me?
Trying to match the available modes, I forced the machine into both 0x11a and 0x11b via the machine configuration and it still went to 1024x768.
Am I missing something here? I did notice the # of colors listed by VESA.exe and those listed in the graphics mode drop down do not match (011a = 64k on VESA util and 16M on graphics mode dropdown). Im not sure if that matters or not.
Am I being too picky and messing with something here that is only going to cause headaches? Its not like 1024x768 doesnt function correctly, its just that resolution on 22 or 24 inch widescreen distorts our company logo pretty bad.
Yeah, I would like to get it displaying at 1280x1024. The default resolution on the monitor I have been doing most of the testing on is actually 1600x1200 (Dell 2007FPb). I havent tried with forcing any of that resolution becuase none of the VESA codes from EM match up with those from the tool, as you indicated would be the case above.