126 replies to this topic

[Galapo]

In some cases where video is unstable, screen is not black, but resolution cannot be adjusted without a prior CDS_RESET. Trouble is, there is no way I know of to programmatically determine when this needed at first boot (of course, when SetResolution is already running and there is a video driver change then there is), so I made the decision to initiate a CDS_RESET when SetResolution starts, that way SetResolution knows the current state of play.

Regards,
Galapo.

[MedEvil]

In some cases where video is unstable, screen is not black, but resolution cannot be adjusted without a prior CDS_RESET. Trouble is, there is no way I know of to programmatically determine when this needed at first boot (of course, when SetResolution is already running and there is a video driver change then there is), so I made the decision to initiate a CDS_RESET when SetResolution starts, that way SetResolution knows the current state of play.

I would guess that it is never needed, when the resolution does not need to be adjusted, because the resolution is already the right one.
Windows i think, issues a reset every time the resolution is changed.
I think SetRes can work the same.

[Galapo]

No, like I said the resolution may be the right one, but it may not be stable. If SetResolution has not been running, it has no way of knowing current stability, hence the need for CDS_RESET just in case. In an unstable situation, if the user were to attempt to adjust resolution with SetResolution, they would not be able to do so. The initial CDS_RESET prevents this glitch.

Regards,
Galapo.

[Galapo]

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

Changes:
- checks are now made before best resolution function attempts to adjust resolution so as to not adjust if not necessary
- improved adjustments made when new device driver is detected
- added ctrl+shift+B hotkey which adjusts resolution to the highest supported resolution of the active display

Regards,
Galapo.

[Galapo]

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

Changes:
- fixed a bug where process priority wasn't set when specified from INI file

Regards,
Galapo.

[Galapo]

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

Changes:
- fixed a bug where under some particular circumstances the LOG wasn't able to be opened

Regards,
Galapo.

[Galapo]

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

Changes:
- added -rebuild commandline parameter, which allows for rebuilding the icon cache
- fixed a bug where if -refresh was specified on commandline and SetResolution was already running, message would indicate such; now no message displays after desktop refresh and second instance of SetResolution closes quitely

Regards,
Galapo.

[Galapo]

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

Changes:
- now compiled with AutoIt v.3.3 resulting in a) the shell icon cache rebuild function being accomplished internally rather than by additional app (dll call in older version didn't allow for the complexity of this function); and b) correct resolutions being reported from display devices so that no "fudged" multiplier is necessary any more
- supports new version of Driver Import PE when released (tomorrow)
- fixed a bug where bestres function wrote to log numerous times after display driver update

Regards,
Galapo.

[Lancelot]

[Galapo]

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

Changes:
- Fixed virtual machine detection bug introduced in previous version due to compiling in newer AutoIt version

Regards,
Galapo.

[Galapo]

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

Changes:
- Changed to a different array sorting function so that program doesn't crash on x64 systems
- Can now specify depth to be set under native and virtual systems upon start

Regards,
Galapo.

[Galapo]

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

Changes:
- Reenabled memory consumption reduction function which was disabled for x64 tests and was forgotten to be enabled when v.5.3 was compiled and uploaded

Regards,
Galapo.

[Zerojinny]

I have a problem whit DisplayProperties.Script and SetResolution.script.
In either do not have a problem when using one.
But the two are used together, the following problems occur.



The boot does not automatically(in registry) run Setresolution After the run manually, the problem does not occur.
In addition, this problem occurs in Vmware , but the problem does not occur in Virtualbox.

SourceCD : XP SP3 Korean
HostOS : XP SP3 Korean
Winbuilder Ver : 080
DisplayProperties.Script Ver : 18
SetResolution.script Ver : 60

[Galapo]

Hi Zerojinny,

I'm on holdays at the moment, so there'll be a delay until I can take a look at the issue.

What happens if you change the RunOnceEx entry in the SetResolution script from 999 to 998?

Regards,
Galapo.

[Zerojinny]

Hi Zerojinny,

I'm on holdays at the moment, so there'll be a delay until I can take a look at the issue.

What happens if you change the RunOnceEx entry in the SetResolution script from 999 to 998?

Regards,
Galapo.

I tried to change RunOnceEx->RunOnce, RunOnceEx->Run and Autostart shortcut.
Interesting thing is when autostart shortcut and run, or when RunOnceEx the appearance of the icon is different.

RunOnceEx's result



Run or Autostart shortcut's result



And i change the RunOnceEx entry in the SetResolution script from 999 to 998 and i got a same result.

Regards,
Zerojinny

[Galapo]

Ok, thanks. What happens if you comment out the resShort.exe lines in buildmodel script?

Thanks,
Galapo.

[Zerojinny]

Ok, thanks. What happens if you comment out the resShort.exe lines in buildmodel script?

Thanks,
Galapo.

I comment out the resShort.exe lines in buildmodel script but it's result was same.
And I tried to move RunOnceEx\999 --> RunOneceEx\000, it means setresolution runs before modelram,
but it's result was same.

[Galapo]

I'm not sure what the root cause of the issue is. But hopefully changing this line

reg_add,0x1,%reg%\Microsoft\Windows\CurrentVersion\RunOnceEx\999,SetResolution,"hiderun %ProgramEXE% -hide -%pScrollBox5% -vmdetect -registry -output"

to this

reg_add,0x1,%reg%\Microsoft\Windows\CurrentVersion\RunOnceEx\999,SetResolution,"hiderun %ProgramEXE% -hide -%pScrollBox5% -vmdetect -rebuild -registry -output"

will fix it for you.

Regards,
Galapo.

[Zerojinny]

Thanks Galapo,

reg_add,0x1,%reg%\Microsoft\Windows\CurrentVersion\RunOnceEx\999,SetResolution,"hiderun %ProgramEXE% -hide -%pScrollBox5% -vmdetect -rebuild -registry -output"

It's not work for me.

To remove runonceex run after the boot is not the problem.
(Start-Run- Setresolution.exe -hide abovenormal vmdetect -rebuid -registry -outpur)

And i have some question.

What's mean "-rebuild"?

Does this issue happen to just me?

[Galapo]

It's not work for me.

Please test it again because that worked for me.

Also, please provide a WinBuilder log of your build.

What's mean "-rebuild"?

It rebuilds the shell icon cache

Does this issue happen to just me?

I get the issue under VMWare. Adding the -rebuild parameter fixed the issue for me.

As for the actual reason why it occurs, I don't know.

Regards,
Galapo.

[Zerojinny]

I tested again it.

This tim I used a English Windows XP as a source.

But i got a same ploblem.

Here is my log.

Before : used -hide -%pScrollBox5% -vmdetect -registry -output




After : used -hide -%pScrollBox5% -vmdetect -rebuild -registry -output

[Galapo]

In the booted PE at a command prompt, type this:

setresolution.exe -exit -rebuild

What happens?

Thanks,
Galapo.

[Zerojinny]

Thanks a lot, Galapo.

It works for me greatly!

How can i add that option?

[Galapo]

I'll have to do some more tests and work out what the best solution is.

Regards,
Galapo.

[Galapo]

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

Changes:
- added -delay commandline parameter to be used in conjunction with -rebuild, which allows for boot-time delay before rebuilding the icon cache (delay is to be specified in seconds, eg -delay=3)
- added log output to specify what resolution was attempted to be set when an error occurs

I've added a script interface option to specify a time for the -delay parameter.

Regards,
Galapo.