Hi everybody,
Lately I have made my launcher modify certain extra settings in the registry, on my XP computer. Now I`m wondering if these registry settings will be valid for Vista and/or Windows 7 as well.
If anybody could send me a copy of the following keys in Vista or Windows 7
(just the .reg file as text)
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU
HKLM\SOFTWARE\Classes\regfile\shell
Thanx very much!!!
Ps.: I promise, one day I will also contribute in making a PortableApp for this site. But first I have to get more common with NSIS (and Windows in general).
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Thanks for continuing with this.
On Vista, HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU does not exist. There is LastVisitedPidlMRU, but that's full of meaningless (seriously meaningless) REG_BINARY values. I'll look for another LastVisitedMRU, just can't remember where it stores all that lot at the moment.
I don't see quite why you want the regfile verb; take a look at the 7-Zip launcher for how we cope with it (that works for all of 98 through 7, it includes two techniques, the first for 98/ME only from memory, the other for 2000 on). Nevertheless, here is what I have for shell\open\MUIVerb=
).
@%SystemRoot%\regedit.exe,-310, and the one you'd really care about, shell\open\command\=regedit.exe "%1"(nice and simpleThese should be the same across Windows 7 as well.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Nice to see you around again, you seem to be the only one reacting to my post. Thanxs
I have finished a `macro` doing the modifying I want. And works fine on XP. I`m actually very happy with the fact that the apps which use this, will directly use the usb-document folder, instead of some local folder. (this just irritated me)
About the 'LastVisitedPidlMRU' you were talking about, I think this is what i`m after. Does it look any thing like the following:
If it looks the same, could you tell me the exact root\path of this key.
If it doesn't look the same, just use regshot and open an app, then open a file through the apps own menu, by clicking 'open file', change to different folder and open a file. It`s important to open a file from a different folder so the MRU will be modified. Make a new shot, the ~res.txt file hopefully includes some value named *MRU* containing the binary code ,every character is followed by a NULL byte. (I really wonder whats the sense of this)
For exaple, in the above the 'a' value contains this string:
i.e.x.p.l.o.r.e.r...e.x.e...C.:.\.D.o.c.u.m.e.n.t.s. .a.n.d. .S.e.t.t.i.n.g.s.\,etc
As well I found out (after spending some time opening as many apps as possible) what happens when the MRUList is full. Strangly enough 'y' is the last letter, but for the rest it behaved as expected. It will use the final letter out of the MRUList string (this one hasn't been used for the longest time), and add this letter on to the front of the string. This I did include in the macro.
Here is the code:
; SetMRUList.nsh ; Copyright: GringoLoco ; License: BSD (NSIS license) !include WordFunc.nsh ; add header for file manipulation !insertmacro WordReplace Function SetMRU Exch $0 ; MRU_PATH Exch Exch $1 ; EXE_NAME Push $2 ;temp function stringtohex string Push $3 ;total hex path value to write Push $4 ;registry::open handle / whole MRUList / temp function StringToHex 2 digit hex number to add Push $5 ;temp function stringtohex lenght of string Push $R0 ;error flag Push $R1 ;registry::find PATH (not used) Push $R2 ;registry::find VALUE / KEY name, used as driveletter in Found: / MRUListLetter Push $R3 ;(part of) registry::find STRING, Value used to compare EXE_NAME Push $R4 ;registry::find TYPE (not used) Var /GLOBAL MRUListLetter StrCpy $3 "" ${registry::StrToHex} "$1" $2 ;turn path into binary StrLen $5 $1 Call StringToHex StrCpy $3 $30000 StrLen $5 $3 ;get lenght of MRUPATH ${registry::Open} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "" $4 SearchLoop: ${registry::Find} "$4" $R1 $R2 $R3 $R4 ;see if lastvisitMRU already exits StrCpy $R3 $R3 $5 StrCmp $R3 $3 Found ;found lastvisitMRU StrCmp $R2 "" NotFound ;didn't find lastvisitMRU Goto SearchLoop NotFound: ${Registry::Close} $4 ${registry::Read} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "MRUList" $4 $R0 StrLen $R2 $4 ;get amount of letters used Intop $R2 $R2 + 97 ;add 97 to make equal to ascii IntFmt $R2 "%c" $R2 ;change in to character StrCmp $R2 "z" FullMRUList ;see if there is a letter available, y is last StrCpy $4 $R2$4 ;add character to MRUList ${registry::Write} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "MRUList" "$4" "REG_SZ" $R0 Goto Write ;write binary string FullMRUList: ${registry::Read} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "MRUList" $4 $R0 StrCpy $R2 $4 "" -1 StrCpy $4 $4 -1 StrCpy $4 $R2$4 ${registry::Write} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "MRUList" "$4" "REG_SZ" $R0 Goto Write Found: ${Registry::Close} $4 ${registry::Read} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "MRUList" $4 $R0 ${WordReplace} $4 "$R2" "" "+" $4 StrCpy $4 $R2$4 ;add character to MRUList ${registry::Write} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "MRUList" "$4" "REG_SZ" $R0 Write: ${registry::StrToHex} "$0" $2 ;change MRUPATH to hex-code StrLen $5 $0 ;get lenght of MRUPATH Call StringToHex ;add NULL byte after every character StrCpy $3 $30000 ;add (double) NULL byte after string ${registry::Write} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "$R2" "$3" "REG_BINARY" $R0 StrCpy $MRUListLetter $R2 Pop $R4 Pop $R3 Pop $R2 Pop $R1 Pop $R0 Pop $5 Pop $4 Pop $3 Pop $2 Pop $1 Exch $0 FunctionEnd Function StringToHex IntOp $5 $5 * 2 Loop: StrCpy $4 $2 2 -$5 StrCpy $3 $3$400 ;add NULL byte after every character IntOp $5 $5 - 2 IntCmp $5 0 "" "" Loop FunctionEnd !macro _SetMRUPath EXE_NAME MRU_PATH Push "${EXE_NAME}" Push "${MRU_PATH}" Call SetMRU !macroend !define SetMRUPath '!insertmacro "_SetMRUPath"'It still needs some code in the launchers script to get the last used path and to save the current path in the launcher ending of course, I could send you that if your interested. (This post will really get to long). All I have to do is make sure it works on the other platforms. But is it really still necessary to make launchers run on '98' !!!
About the classes, that WAS just some other situation I came across. I have got one app, which writes classes by it self, and the launcher has to restore the keys afterwords. Got this to work fine, and for a moment I thought this would be wicked for all apps. I left this project for now, realizing that if all apps would do this by there self, the registry could/would really get messed up. I still think it could be done, but the code would be very extreme for what it does.....
Ok, probably I should include the rest of the script as well:
; insert default MRU path, the app will open/save files to this path on the portable drive by default. !define MRUPATH "Documents\Pictures" ; rest of your own script ; script to add before updating the roots in settings files, cause it needs the lastdriveletter Var /GLOBAL FilesOpenMRUPATH ${GetRoot} $EXEDIR $0 ReadINIStr $R4 "$DATADIR\Settings\${PNAME}Settings.ini" "PortableSettings" "LastDrive" ReadINIStr $3 "$DATADIR\Settings\${PNAME}Settings.ini" "PortableSettings" "LastMRU" StrCpy $4 $3 2 ;get last MRU driveletter ${If} $3 == "" ; see if ini-parameter exists StrCpy $FilesOpenMRUPATH $0\${MRUPATH} ;if not use default ${Else} ${If} $4 == $R4 ;if lastdrive letter equals last MRU drive letter StrCpy $3 $3 "" 3 ;remove last MRU driveletter StrCpy $FilesOpenMRUPATH $0\$3 ;add current driveletter and lastMRUpath ${Else} ;last drive doesn't equal to last MRU letter, use default StrCpy $FilesOpenMRUPATH $0\${MRUPATH} ${endif} ${EndIf} ${SetMRUPath} ${EXE} $FilesOpenMRUPATH ; rest of your own script, including ${replaceinfile}.... ; Run App ; save current MRU path ${registry::Read} "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\LastVisitedMRU" "$MRUListLetter" $3 $R0 ${WordReplace} $3 "00" "" "+" $3 ;remove all NULL bytes ${Registry::HexToStr} $3 $3 ;change into hex-code ${WordFind} $3 ".exe" "+2" $3 ;find string containing path WriteINIStr "$DATADIR\Settings\${PNAME}Settings.ini" "PortableSettings" "LastMRU" $3Please, feel free to give me any tips and trick about my coding, cause I`m just a beginner.
For the moment I've just been making every app, I used to have installed, portable for my own use(they are mainly not open-source). But since PA.c also accepts freeware:)
:smile:, probably there are some apps I will contribute to PA.c soon.
Ps.: I done some last minute changes on this last script, to make it compatable with the standard PA.c apps, hope I didn`t mess it up!!!
Anyway, I will not be on the forum till next weekend, cause of exams.
Formerly Gringoloco
Windows XP Pro sp3 x32
The null bytes are there because these values are in Unicode, which is also why they end with 3 null bytes.
You asked for it
The reason I didn't think it could be the one was the very lack of the index string - I'm vaguely familiar with it on Windows 2000 and XP, and so, missing it, decided it probably wasn't the one. I'm not sure. The explanation about the null byte being for Unicode makes sense
I'm also not on here much for the next several weeks, as I'm doing my exams, starting on Friday.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Hope you do well in your exams.
The index string you are looking for is the MRUListEx entry. Except it has changed from a string to an array of dword's. Here is the format as I see it:
the last one '0xffffffff' does the same for this format as the 2 null bytes in unicode does.
As for the entries themselves, they are still unicode.
To get the right numbers for the entries, just convert the dword's from hex to decimal.
Microsoft probably changed to this format to support a much bigger amount of entries.
I need to find another way of making a launcher realize a switch of PC, besides just checking the drive letter. Cause drive letter doesn't all ways change switchin PC's!
I thought my self about checking for windows registration keys, cause they should be personal.
On my XP computer I found the following registry keys:
I am hoping Vista & Windows 7 are also making use of any of these keys ?
Or would there be a better way of having a launcher realize every switch of PC ?
Formerly Gringoloco
Windows XP Pro sp3 x32
On Vista HEKY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProductId contains the registration key. The other two do not exist.
I'm not sure about this as the best way to handle it, but I don't know what would be a better way. You could read the drive serial number. I'm not sure whether either of these techniques work in WINE though.
Why do you need to detect if it's a different machine? Is it to do with the user or machine or some combination or something else? Knowing why you need it might help.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
for your reply !
I need this for Winamp launcher. The problem is the playlists, when there would be a fair amount of song file names in a playlist but located on the PC it self. Winamp would get 'frozen' on a different PC, cause it spends all it's energy in looking for these files (which don't exist anymore).
The launcher is able to clean up the playlists after a drive letter change, but when ever you would switch to a PC which uses the same drive letter it wont happen.
Maybe detecting HDD serial number could do the trick as well, would it be better?
And how would I make the launcher check this ?
Formerly Gringoloco
Windows XP Pro sp3 x32
; $0 - Drive to check returns the Disc Serial Number Function GetDiskVolumeSerialNumber !define GetVolumeInformation "Kernel32::GetVolumeInformation(t,t,i,*i,*i,*i,t,i) i" System::Call '${GetVolumeInformation}("$0",,${NSIS_MAX_STRLEN},.r0,,,,${NSIS_MAX_STRLEN})' FunctionEnd ;GetDiskVolumeSerialNumber ; To view Disc Serial Number in hexsadecimal format ;IntFmt $0 "%08X" $0This does the trick !
Can I count on the existence of a drive C: on every PC, or could there be PC's about without a C: drive ?
But on a quick test I just done, it doesn't show serial number of my D: drive.
As I am writing this, I realize, probably it doesn't because it's just a partition of the main drive!!!
Will do some testing with it, thanx a lot Chris !
Talking about the NSIS forum, would you be a member of the forum ?
I am having a hard time becoming a member of the Winamp forum (which I suspect/hope is connected to the Winamp forum) !
I just want to get in contact with them, so I could be a member and add some topic(s) about making Winamp Portable. (quite important !!!)
The forum just seems to be closed for anybody, at the moment !
Formerly Gringoloco
Windows XP Pro sp3 x32
ReadEnvStr $0 SystemDrivewill find you the system drive (normallyC:). Volume information may or may not do it, but it's definitely worth a try. Personally I would do it like so:!define _GetVolumeInformationSysCall "Kernel32::GetVolumeInformation(t,t,i,*i,*i,*i,t,i) i" !macro GetDiskVolumeSerialNumber _SERIAL _DRIVE Push $0 System::Call '${_GetVolumeInformationSysCall}("${_DRIVE}",,${NSIS_MAX_STRLEN},.r0,,,,${NSIS_MAX_STRLEN})' Exch $0 Pop ${_SERIAL} !macroend !define GetDiskVolumeSerialNumber "!insertmacro GetDiskVolumeSerialNumber"Then you could use it so:
ReadEnvStr $0 SystemDrive ${GetDiskVolumeSerialNumber} $1 $0\And $1 will have the drive serial number in it.
I went and updated the NSIS wiki page about this technique while I was at it as it seemed a good sort of thing to do. I might see if I can get this to go into FileFunc.nsh for the next release of NSIS, it might be useful to people.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Thanx so much for all your feedback!
You are a NSIS genius !
With this code I am getting a serial number for my D: drive (partition) as well. Even it seems to be a different serial number (-534190393) than the system C: drive (2018447845). Strange, but good!
But, you must have made a typing error. I did get the decimal one working after adding some quotes :
ReadEnvStr $0 SystemDrive ${GetDiskVolumeSerialNumber} $1 "$0\"But the hexadecimal one I got from the Wiki page, I didn't get to work, even with the quotes : (I did use the script from the NSIS wiki page)
; Or find it as hex ${GetDiskVolumeSerialNumberHex} $1 $0\The error tells me the macro requires 2 parameters, but passed 4 (5 including the qoutes)!
Now I remember your ChrisLauncher script, nice the way you make use of the macros. Maybe I could use them in my script to clean things up a bit.
All I don't like is that they need to be in the start of the script (which I think makes the script a bit messy) or I have to include them as a .nsh file!
By just using functions, I could locate them on the end of the script!
Anyway about the NSIS forum, I meant this one NSIS-Forum
Are you a member on this forum ?
What's the story there, why don't they allow new members ?
Formerly Gringoloco
Windows XP Pro sp3 x32
GetDiskVolumeSerialNumberHex should be called separate from GetDiskVolumeSerialNumber - don't run one and then the other on the same input.
Also you can try putting quotes around %08X.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
is by leaving out the backslash on the end !
Is the back slash really that important.
Not sure what you meant with :
I have been using the decimal or the hex one in separated tests.
Anyway, it's not such a bad problem, just interested why it is (not) working the way it is !
Formerly Gringoloco
Windows XP Pro sp3 x32
Don't check the registration key. When I download Windows 7, I got all six of the keys. Then it started repeating. (This is because I had to try to download it a bunch of times.)
What you should do is compare the drive letter in the INI and the current drive letter. OR are you needing it for something different?
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
Hi Oliver,
Sorry, but don't really understand your comment ?
Do you mean that I shouldn't make the launcher compare registration keys, to realize switch of PC ?
Because Windows 7 doesn't use one of these registry keys ?
Would it be better to check for HDD serial number ? (see answer to Chris, just above)?
Anyway, comparing drive letters isn't good enough for this job ?
Thanx for the feedback !!!
Formerly Gringoloco
Windows XP Pro sp3 x32
Do not use registration keys as a way to tell if the computer has been changed.
They are recycled among Windows PC's
I would definitely use the drive serial as that should never exist anywhere else.
If you say so
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world