Jump to content

Resolution reverts back to VGA (640x480) after SECOND boot


Recommended Posts

Topic title is quite clear... I do not understand why this is .. ?

Full installation runs @ 1024, first boot is also 1024, but when I reboot, then the resolution is reverted to 640...

quite strange, and quite irritating... Somebody knows what I am doing wrong ?

PS:

WINNT.SIF:

[Display]
BitsPerPel=32
Xresolution=1024
Yresolution=768
Vrefresh=60
AutoConfirm=1

HIVESYS.INF:

[AddReg]
HKLM,"SYSTEM\CurrentControlSet\Services\VgaSave\Device0","DefaultSettings.BitsPerPel",0x00010001,32
HKLM,"SYSTEM\CurrentControlSet\Services\VgaSave\Device0","DefaultSettings.XResolution",0x00010001,1024
HKLM,"SYSTEM\CurrentControlSet\Services\VgaSave\Device0","DefaultSettings.YResolution",0x00010001,768
HKLM,"SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.BitsPerPel",0x00010001,32
HKLM,"SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.XResolution",0x00010001,1024
HKLM,"SYSTEM\CurrentControlSet\Control\Video\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.YResolution",0x00010001,768

Edited by Jeroeneke
Link to comment
Share on other sites


What does the AutoConfirm=1 in your winnt.sif mean? I can't find any reference to this in the documentation. I'd leave out the registry entries you mentioned in hivesys.inf if I were you; as far as I know these shouldn't be necessary and may very well be the cause of the problem.

Link to comment
Share on other sites

The reg keys are used to make the installation running at 1024 ;)

My winnt.sif is quite old (for about a year now) so I have kind of forgotten what it means, will search for it, if I don't find anything, I will delete it ;)

I will test an installation without those reg keys and see what it does. But if I do that, the instalaltion runs at 640, first boot will also be 640, so I don't think I will see it by this...

Link to comment
Share on other sites

What does the AutoConfirm=1 in your winnt.sif mean? I can't find any reference to this in the documentation. I'd leave out the registry entries you mentioned in hivesys.inf if I were you; as far as I know these shouldn't be necessary and may very well be the cause of the problem.

AutoConfirm=1

This will disable the really annoying box the appears upon first logon if the resolution wasn't properly set. It's the popup that says your current resolution isn't correct for Windows XP.
Link to comment
Share on other sites

AutoConfirm=1
This will disable the really annoying box the appears upon first logon if the resolution wasn't properly set. It's the popup that says your current resolution isn't correct for Windows XP.

I see, thanks! Can't find any information about this option in the Preinstallation Reference though... After a bit of searching I'm guessing this is a leftover option from the Windows NT 4.0 days?

Link to comment
Share on other sites

It sounds to me that the AutoConfirm may actually be the problem in this case though. If you change the video back to the higher res. will it stay there after a couple of reboots?

Edited by VCC
Link to comment
Share on other sites

Well, unless someone else has a better idea, I would say, "Yes, try it without that setting." Although, it does sound like a helpful setting otherwise.

Another suggestion would be (just for troubleshooting) to try kicking down the BitsPerPel=32 to 24 rather than 32. Or remove the Vrefresh=60, maybe try a lower setting there, maybe 70 or 75. You could be pushing it to hard in the beginning. I know that's the idea, but something is not liking that idea much.

Link to comment
Share on other sites

Well, unless someone else has a better idea, I would say, "Yes, try it without that setting." Although, it does sound like a helpful setting otherwise.

Another suggestion would be (just for troubleshooting) to try kicking down the BitsPerPel=32 to 24 rather than 32. Or remove the Vrefresh=60, maybe try a lower setting there, maybe 70 or 75. You could be pushing it to hard in the beginning. I know that's the idea, but something is not liking that idea much.

I think you have misread a bit, it's 60Hz I have (nog 80 ;) )

Reason therefore is that I install on a laptop which only have 60Hz screens (in most cases). I will try it out whithin some minutes, and will let you know the result

Link to comment
Share on other sites

Tested it without that line in WINNT.SIF, and there wasn't any difference in the installation... Everything stayed the same...

My guessing is, that something hapens at the first boot with the resolution settings (I have a small software installation at first boot too). Something that makes the standard resolution back to 640*480 or something ? Somebody can confirm ?

Link to comment
Share on other sites

Full installation runs @ 1024, first boot is also 1024, but when I reboot, then the resolution is reverted to 640...

This happened to me on a DELL INSPIRON 1300.

Resolution was set to 800x600 in WINNT.SIF and in a reg tweak (at T-13), too.

I haven't put AutoConfirm=1 in WINNT.SIF nor I edited hivesys.inf, either.

After Windows finishes its SETUP (T-9 and beyond) and reboots, the Administrator account gets logged on automatically.

Some apps are installed, two user accounts are created, and some tweaks & cleaning are done. The computer reboots again.

The computer logs on the first user account automatically.

Some apps are installed, and some tweaks & cleaning are done. The computer reboots again.

The computer logs on the second user account automatically.

Some apps are installed, and some tweaks & cleaning are done. The computer reboots again.

NB: HKLM\..\RUN is used to launch a CMD to do all the above for each user account.

So, I SAW each user's DESKTOP set to 800x600!!

Now, it's time for the logon screen to come up where a user must click his name and type his password in.

At the logon screen, resolution is set to 640x480. I couldn't have an overall view of the logon screen.

I could hardly click the second user name and type the paasword in.

Well! The second user is finally logged on. And, its DESKTOP is also, 640x480!!!

I could, manually, change the resolution back to 800x600. (from Display Properties)

And 800x600 sticks for all user accounts, afterwards.

Looking for a permanent solution, the first thought to come to my mind is to open the Device Manager.

Surprisingly, there's no Display Adapter defined under Device Manager!

There's an undefined Video Controller (of yellow question mark), instead.

What I did was that I installed S/W driver for the Video Controller. I took a shot to collect installed files.

I added those files to a new UACD and tested again. And the problem is solved.

HTH

Link to comment
Share on other sites

  • 1 year later...

As I posted this Video Resolution Windows Setup tweak several years ago I did not monitor the registry closely. While testing on VMWARE is different from a real system it was annoying to see the display get set at 640x480 after second reboot.

So at last here is a fixed version of this tweak:

;Disable Screen Resolution balloon tip
HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\DontShowMeThisDialogAgain","ScreenCheck",0x0,"no"
;Change default resolution to 1024x768x32
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","Attach.ToDesktop",0x10001,0x1
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.BitsPerPel",0x10001,32
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.XResolution",0x10001,1024
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.YResolution",0x10001,768
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.VRefresh",0x10001,0x1
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.Flags",0x10001,0x0
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.XPanning",0x10001,0x0
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.YPanning",0x10001,0x0
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.Orientation",0x10001,0x0
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","DefaultSettings.FixedOutput",0x10001,0x0
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","Attach.RelativeX",0x10001,0x0
HKLM,"SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000","Attach.RelativeY",0x10001,0x0

Edited by Acheron
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...