x: is the drive letter of winpe (ramdisk)

but the drive letter of winpe drive is different. maybe c: ... e: ... or f: ?

run my utility and the drive letter of winpe disk is y: always.

sample of winpeshl.ini:
[LaunchApps]
setlw.exe
cmd.exe

attention: set the label of winpe drive (usb stick or usb hdd) to "something_pe_something" (sample: "usb_pe_") !!!

64bit version of setlw.exe available on request...

If your app is using a different method than this; http://www.msfn.org/board/topic/149173-win...-c-or-anything/ (registry tweak) then I would like you to also outline what your app actually does. Thanks.

it is an alternative method compared to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices . but better.

the winpe systemroot is x: normally. but the winpe bootdrive is different!

Sure , the question joakim asked (and that I am now asking too) is actually:


For the record, this ONLY applies to PE 2.x and 3.x (Vista or Windows 7 based), right?


jaclaz

its simple winapi...

1. GetVolumePathNamesForVolumeName
---> search label "*_pe_" and read VolumeMountPoint
2. DeleteVolumeMountPoint (remove drive letter)
3. SetVolumeMountPointA (set drive letter to y:)

should work in old xp pe also (but not tested).

Good , and where are those settings "deleted from" and "written to"? (I mean if not to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices ? )

Isn't this the same as running MOUNTVOL?

Like:



jaclaz

Why are you giving the guy a hard time? He wrote a utility that is easy to use ( it takes no params ) and I presume it works. Either use it or don't use it.

I am not trying to give him a hard time, I am sorry if it sounded like that .

I am only trying to understand what it does, and how it does it.

Or, if you prefer, joakim here:
http://www.msfn.org/board/topic/149173-win...-c-or-anything/
posted about a new (AFAICR) interesting approach, and I was trying to understand whether the present thread may be useful for that or it simply represents (as it does) a nice tool to do something we already know about.


Wonko

Like jaclaz (including myself) is trying to say, is it would be nice and informative for current and future reference if you would describe in detail what your tool actually does and how it does it. I ask because I'm interested in learning new things..

Joakim

memset..MSVCRT.dll....GetModuleHandleA....HeapCreate..(.FindFirstVolumeA..|.GetV
olumeInformationA...GetVolumePathNamesForVolumeNameA....DeleteVolumeMountPointA.$.SetVolumeMountPointA..3.FindNextVolumeA.;.FindVolumeClose...HeapDestroy...
ExitProcess.KERNEL32.dll..+.Sleep...HeapAlloc...HeapFree....HeapReAlloc...StrStrI
A..SHELL32.DLL...timeBeginPeriod...timeEndPeriod.WINMM.DLL

should be informative

Kind of. But instead of spending time on reverse engeneering the app, I would like the author to explain the stuff himself/herself.

He already did in post 5. Exactly the same way as I use and which is documented by MS.

See here for details:

http://msdn.microsoft.com/en-us/library/aa...v=VS.85%29.aspx

This is nice! Thank you very much for this utility.

Could you post or email 64 bit version?

Sure. What's you're email address? Or your home address if you want a CD? Which 64 bit PE do you want? Win 8, Win 7, XP, Server edition?

I was referring to 64 bit version of this utility: setlw.zip ( 1.31K )
that was the subject of the post by Pitty.

Good to hear. I was being facetious with my prior reply.

please.. .