JohnFx's Posts

I tried that to no avail. I took a registry file that previously built with no complaints and added a line "#this is a comment" somewhere in the middle of it and the build process errors out with... See more...
I tried that to no avail. I took a registry file that previously built with no complaints and added a line "#this is a comment" somewhere in the middle of it and the build process errors out with "Expected isolation mode or deleted at..."
I'd like to add some commenting to these files to document why I am isolating each key. Is there a comment character that can be used in these files?
Okay, I think I have discovered the issue and it appears that not all objects were being treated the same with respect to whether it affected the host system or not. This Approach... See more...
Okay, I think I have discovered the issue and it appears that not all objects were being treated the same with respect to whether it affected the host system or not. This Approach will write to the host system registry regardless of the isolation Sub SetStringKey_HKLM(KeyPath,KeyName,Value) const HKEY_LOCAL_MACHINE = &H80000002 Computer = "." Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}! " & Computer & "\root\default:StdRegProv") oReg.SetStringValue HKEY_LOCAL_MACHINE,KeyPath,KeyName,Value End Sub This approach seems to operate inside the context of the virtual bubble Sub SetStringKey_HKLM(KeyPath,KeyName,Value) Set WSHShell = CreateObject("Wscript.Shell") WSHShell.RegWrite "HKEY_LOCAL_MACHINE\" & KeyPath & "\" & KeyName, Value,"REG_SZ" End Sub
Are you absolutely sure about this. I isolated (with write_copy isolation) the exact key my script was modifying and it still affected the registry on the host system. I am writing to the key i... See more...
Are you absolutely sure about this. I isolated (with write_copy isolation) the exact key my script was modifying and it still affected the registry on the host system. I am writing to the key in the OnFirstSandboxOwner callback, perhaps this callback behaves differently?
I think I might need to clarify my question based on your answer. I am talking about the .VBS scripts that are built into the package and run at startup of the package. I was under the impression... See more...
I think I might need to clarify my question based on your answer. I am talking about the .VBS scripts that are built into the package and run at startup of the package. I was under the impression that those run outside the context of the virtual environment, so I don't see how modifying the virtual registry keys would help.
I've written a thinApp script to dynamically create some registry keys when the package starts up and it seems to be working okay. However, it is writing the registry keys to the host system an... See more...
I've written a thinApp script to dynamically create some registry keys when the package starts up and it seems to be working okay. However, it is writing the registry keys to the host system and not the virtual environment. Is there any way to make the script run within the virtual environment, or alternately write to the virtual registry explicitly in a script? Folling is the code I am using to write the keys. Sub SetStringKey_HKLM(strKeyPath,KeyName,strValue) c onst HEY_LOOCAL_MACHINE = &H80000002 strComputr = "." Set oReg=GetOect(twinmgmts:s:mpersonanaonLevel=impersonatate}! " & strComput & "\root\d\default:StdRegPro) oReg eg.SetSngVague HKEY_LOCAL_AL_MACHINE,strKeyPateyName,strsalue End Su Sub
I did some testing and I don't think that is the issue. Would you concur based on this test? 1) Delete the sandbox directory from my local system 2) Run the packaged EXE from a networ... See more...
I did some testing and I don't think that is the issue. Would you concur based on this test? 1) Delete the sandbox directory from my local system 2) Run the packaged EXE from a network location (problem is exhibited) 3) Check sandbox location on my system (it was created in the expected place)
I have virtualized some Internet Explorer plug-ins and browser settings using IE as the entry point. When I run the package everything seems to work correctly. However, if I copy the EXE file u... See more...
I have virtualized some Internet Explorer plug-ins and browser settings using IE as the entry point. When I run the package everything seems to work correctly. However, if I copy the EXE file up to a network share and run it from that location it seems to ignore the virtual registry altogether. For example, in my virual registry built into the package I set the homepage on the browser to a specific site. When I open the exe from anywhere on my local machine that homepage comes up correctly. If I copy the same exe up to a network share and double click that instance the homepage is back to the IE default along with the other settings that are built into the virutal registry. Should it matter where the actual EXE is located? It seems to.