Set the time within the sandbox
Set the time within the sandbox
Hi,
I was wondering if it would be possible to add a feature to the sandbox so that programs within the sandbox runs with its own time separate from the main time of the system?
I was wondering if it would be possible to add a feature to the sandbox so that programs within the sandbox runs with its own time separate from the main time of the system?
Re: Set the time within the sandbox
This was requested and the answer was "no".newbie wrote:Hi,
I was wondering if it would be possible to add a feature to the sandbox so that programs within the sandbox runs with its own time separate from the main time of the system?
You can use the search function if you want to know why.
A small Programm called RunAsDate from NirSoft could help you.
Start it inside the Sandbox, set the Date/Time and your Programm's destination, perhaps some startparameters and run it.
Only .exe possible, sadly no .bat or .com yet.
http://www.nirsoft.net/utils/run_as_date.html
Start it inside the Sandbox, set the Date/Time and your Programm's destination, perhaps some startparameters and run it.
Only .exe possible, sadly no .bat or .com yet.
http://www.nirsoft.net/utils/run_as_date.html
Well, in the File-Open-Dialog I've just looked at the possible Extensions and saw nothing but .exe
This was the reason why I assumed that only .exe will work.
Using the Date and Time Command inside C:\WINDOWS\system32\cmd.exe works well.
But running with C:\WINDOWS\system32\command.com shows the original System Date/Time.
I've created two Batchfiles.
One with C:\WINDOWS\system32\cmd.exe and another with C:\WINDOWS\system32\command.com inside.
Both are showing successfull the forced Date/Time.
But running another instance of cmd.exe or command.com inside the first one shows the original System Date/Time.
Just like the test with the parameter /c C:\WINDOWS\system32\cmd.exe
This was the reason why I assumed that only .exe will work.
Using the Date and Time Command inside C:\WINDOWS\system32\cmd.exe works well.
But running with C:\WINDOWS\system32\command.com shows the original System Date/Time.
I've created two Batchfiles.
One with C:\WINDOWS\system32\cmd.exe and another with C:\WINDOWS\system32\command.com inside.
Both are showing successfull the forced Date/Time.
But running another instance of cmd.exe or command.com inside the first one shows the original System Date/Time.
Just like the test with the parameter /c C:\WINDOWS\system32\cmd.exe
MaSc wrote:A small Programm called RunAsDate from NirSoft could help you.
Start it inside the Sandbox, set the Date/Time and your Programm's destination, perhaps some startparameters and run it.
Only .exe possible, sadly no .bat or .com yet.
http://www.nirsoft.net/utils/run_as_date.html
Thx a lot. It worked great.
-
- Posts: 1
- Joined: Thu Mar 14, 2013 10:31 pm
I'm currently running some program, zm.exe, which needs to access a certain driver file. So even if I run the main zm.exe program with "runasdate" (or similar software), the driver file zm.exe looks for still manages to read the system actual system time.
Sadly, I really need to find a way to change the system time to 2010 within sandboxie =( I could do this outside Sandboxie but if I do so, I couldn't run MS word simultaneously as I run zm.exe.
Sadly, I really need to find a way to change the system time to 2010 within sandboxie =( I could do this outside Sandboxie but if I do so, I couldn't run MS word simultaneously as I run zm.exe.
Who is online
Users browsing this forum: No registered users and 1 guest