Jump to content











Photo
- - - - -

[app script] SetResolution


  • Please log in to reply
126 replies to this topic

#51 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 09 May 2008 - 09:28 AM

Script has been updated with version 2.4 of SetResolution.exe.

SetResolution now has no need for bestres.exe or rescopy.exe as supported resolutions are obtained directly from windows api. (Many thanks to rasim's post here which has allowed me to do this). This means hopefully the 64bit version is now functional, but I can't test for lack of an environment to do so.

Regards,
Galapo.

#52 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 12 May 2008 - 06:08 AM

Script has been updated with version 2.5 of SetResolution.exe.

ctrl + shift + L sets "low" resolution of 640x480 with the addition now of setting also "low" colour depth of 256 colours.

Regards,
Galapo.

#53 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 12 May 2008 - 10:05 AM

Script has been updated with version 2.7 of SetResolution.exe.

Fixed a bug under Win2k. Made some function changes for compatibility for 64bit version (which is hopefully working now!).

Regards,
Galapo.

#54 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 13 May 2008 - 01:19 AM

Script has been updated with version 2.8 of SetResolution.exe.

Changes:
- makes necessary file check for needed file msvcrt.dll
- vmdetect.exe is now only run when -vmdetect is specified as a commandline parameter (good for when running stand-alone on normal OS as vmdetect run is unnecessary)


Regards,
Galapo.

#55 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 16 May 2008 - 02:22 AM

Script has been updated with version 2.9 of SetResolution.exe.

Changes:
- hotkeys now step up/down in a more measured fashion so that the process doesn't get ahead of itself in the case of multiple press or holding down a key

Regards,
Galapo.

#56 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 18 May 2008 - 09:33 AM

Script has been updated with version 3.0 of SetResolution.exe.

Changes:
- implements some error checking regarding the success or otherwise of changing of resolution
- if resolution was not successfully adjusted up/down, an attempt is made to adjust to the next highest supported resolution before reporting the error
- a ChangeDisplaySettings CDS_RESET is initiated at program start

Regards,
Galapo.

#57 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 19 May 2008 - 12:28 AM

Script has been updated with version 3.1 of SetResolution.exe.

Changes:
- fixed an error on (optional) startup message introduced with changes made to 3.0.

Regards,
Galapo.

#58 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 18 June 2008 - 09:38 AM

Script has been updated with version 3.2 of SetResolution.exe.

Changes:
- at the request of darkman738, SetResolution can now set resolution entered from commandline, eg 'SetResolution -r1024x768'.

Regards,
Galapo.

#59 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 04 July 2008 - 09:28 AM

Script has been updated with version 3.4 of SetResolution.exe.

Changes:
- can now set colour depth from commandline, eg 'SetResolution -r1024x768x32' or to use current resolution 'SetResolution -r-1x-1x32'
- gui-style about/help dialogue rather than message box at program start if -hide parameter isn't specified (better for low-resolution scenario)

Regards,
Galapo.

#60 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 31 July 2008 - 02:54 AM

Script has been updated with version 3.7 of SetResolution.exe.

Changes:
- fixed bug when running under native machine when -output wasn't specified
- fixed bug in PE with vgasave device setting resolutions too high on crt monitors where refresh rate was too high

Notes:
1) When calling EnumDisplaySettingsEx, I had first thought not setting EDS_RAWMODE would be enough as per MSDN note. However, if only generic vgasave device is utilised at PE, then it seems that with crt monitors, returned supported resolutions may indeed be too high for refresh rate. Trouble is, we have no way of knowing (to the best of my knowledge) of obtaining the proper rate as rates returned from EnumDisplaySettingsEx for vgasave device are simply given as "default" -- but we don't know the "default".
2) To get around this issue, if vgasave device is detected when attempting to set highest supported resolution under PE, no attempt is made to set this resolution. Instead, the following resolutions are attempted to be applied in the following order: 1024x768; 1152x864; 1280x800; 1280x1024.
3) If when manually adjusting resolution up with ctrl+shift+uparrow results in resolution setting being detectably unsuccessful, then no further attempts at adjusting higher are made (contrary to previous versions) and resolution remains as before attempt.
4) Given 3) above, if when manually adjusting resolution up with ctrl+shift+uparrow results in crt monitor losing sync, obtaining view again is easy (without having to resort to ctrl+shift+L) by adjusting down with ctrl+shift+downarrow.

Regards,
Galapo.

#61 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 22 September 2008 - 06:22 AM

Script has been updated with version 3.9 of SetResolution.exe.

Changes:
- adds commandline option -refresh to refresh screen.

Regards,
Galapo.

#62 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 November 2008 - 05:59 AM

Script has been updated with version 4.1 of SetResolution.exe.

Changes:
- now detects primary driver change and makes adjustments accordingly.

Regards,
Galapo.

#63 billonious

billonious

    Silver Member

  • .script developer
  • 527 posts
  • Location:greezeland
  • Interests:curiosity

Posted 06 November 2008 - 07:47 PM

Hey galapo,

:cheers:

Does "set resolution" script come to conflict with "Display properties" one by Holger Kotsch?
I noticed that they both try to set resolution.

regards,
bill

#64 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 November 2008 - 07:52 PM

Yes and no.

No in the sense that Display Properties script adds all the stuff necessary for display etc.

Yes in the sense that SetResolution overwrites the display set by Display Properties.

Regards,
Galapo.

#65 billonious

billonious

    Silver Member

  • .script developer
  • 527 posts
  • Location:greezeland
  • Interests:curiosity

Posted 06 November 2008 - 08:12 PM

:cheers:
express response!

#66 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 November 2008 - 08:19 PM

I do try to please!

But in this case it was a fluke: I'd just logged in after a night of rest.

Regards,
Galapo.

#67 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 11 November 2008 - 08:38 PM

Script has been updated with version 4.2 of SetResolution.exe.

Changes:
- now can run portably from an INI file (SetResolution.ini).
- if SetResolution.ini is not found in the same folder as SetResolution.exe, a default SetResolution.ini file is generated (if folder is writable).
- INI specifications follow commandline options.
- if SetResolution is called with commandline options, commandline options are given preference over INI options.
- INI may be kept but disabled by specifying 'UseINI=False'.

Regards,
Galapo.

#68 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 11 November 2008 - 09:07 PM

Very nice idea!

:cheers:

#69 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 16 November 2008 - 03:32 AM

Script has been updated with version 4.3 of SetResolution.exe.

Changes:
- About-GUI bugfix as change introduced in 4.2 resulted in fullpath of %temp% being expanded

Regards,
Galapo.

#70 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 17 November 2008 - 04:13 AM

Script has been updated with version 4.4 of SetResolution.exe.

Changes:
- fixed a bug with an internal variable change introduced with v.4.3
- few enhancements to log generation

Regards,
Galapo.

#71 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 23 November 2008 - 08:30 AM

Script has been updated with version 4.5 of SetResolution.exe.

Changes:
- added option of ctrl+shift+O to open LOG file if it exists (with default txt editor)

Regards,
Galapo.

#72 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 26 November 2008 - 04:01 AM

Script has been updated with version 4.6 of SetResolution.exe.

Changes:
- resolutions are now sorted firstly on colour depth rather than size -- this means that resolutions are only sized up/down in relation to the currently set colour depth
- ctrl+shift+L colour depth now set to 16-bit rather than 8-bit
- two displays are now supported

- ctrl+shift+1 sets display1 as active (for resolution change) and toggles attachment

- ctrl+shift+2 sets display2 as active (for resolution change) and toggles attachment

- ctrl+shift+A shows which display is set as active for resolution change

- ctrl+shift+C hotkey added, which displays the current resolution of the active display

Regards,
Galapo.

#73 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 26 November 2008 - 11:43 AM

When LiveXP boots up the screen flashes a few times, don't know if that's the fault of SetResolution.
So my question is, upon start does setRes check first which resolution is the active one before applying the set startup resolution?

:)

#74 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 26 November 2008 - 08:07 PM

You are probably correct, but I'll look into it soon. My initial guess is that a check is not made, so I'll make it do a check to avoid unnecessary flashes.

At least one flash is unavoidable as SetResolution does a CDS_RESET when it first starts to guarantee that the video state is stable (eg, in case of prior hwpnp run where new video driver has been installed).

Regards,
Galapo.

#75 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 26 November 2008 - 08:27 PM

At least one flash is unavoidable as SetResolution does a CDS_RESET when it first starts to guarantee that the video state is stable (eg, in case of prior hwpnp run where new video driver has been installed).

That point i don't get. If the screen stays black we have the reset command. In all other cases the video needs no fixing, as it is working corectly. Or?

:)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users