I've seen similar programs out there but, none that quite meat this idea. I'm just starting to learn programming and I'm not in a class (yet) so I only know some of the basics. The idea is to create a small program in the computers RAM or Virtual RAM that would act like a registry. The program would be considered to be the registry by other programs thus allowing a fake registry. The program would, of course, have to save it's registry entries in a portable file for easy repeated use. It would use a hierarchy system so it could use the real registry with the fake one. This way I could say open the program and install Java to my portable firefox then, when I'm on a restricted computer that doesn't support it I could simply activate the program then Firefox and fool the Firefox into thinking it was using the real registry. In a similar fashion I could use other programs that are just too registry dependent or not open source on any computer.
I hope this makes sense to those who read it, I unfortunately have troubles from time to time conveying what's in my head to others.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
My first post was kind of long but, had the basic idea so I don't wish to delete it. To make things a little more clear, and hopefully get some traffic, here's a few bullet points for the potential project.
A folder would be created either in the main portable apps folder (next to the launcher) or in the apps subfolder to contain the program and 'fake' registry.
When active the program (I'm calling it RegSim for now) would simulate a windows registry with a hierarchy system to incorporate the 'real' registry but, without actually writing to the 'real' registry (so it's visible only when active).
It would have it's own installation wizard so it could install programs and automatically record all the reg entries into itself.
It could potentially become part of PAM
If necessary the program could launch the would be portable apps itself but, the idea is that it would recognize anything in the apps subfolder as one it's 'fake' portable apps.
I would include a pectoral representation but, I don't have the artistic skills or a readily accessible scanner. (I have one at home but, I've not been able to use that computer.
Do you know how to implement it?
Maybe I underestimate your capabilities or don't see the right solution, but this looks like a task for much more experienced programmer.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
I don't really know anywhere near enough to program this kind of thing, that's why I put it in the request apps forum. I was hoping someone with the knowledge and experience could make this. The ideas I put in here are things I've seen or are similar to things in other programs.
You're asking for an app like Sandboxie. Like Sandboxie, an app for this purpose would need a kernel mode driver, and would not be truly portable.
He had to use AutoIt which isn't generally permitted but, can be downloaded separately and is portable itself. The app monitors registry folders when you install programs so I don't see why a fake one couldn't be created. I am admittedly limited in my programming knowledge though.
I admit that I didn't check it, but I guess that it doesn't monitor changes, but rather makes a backup before anything happens and compares it to what's inside after you're done with testing.
This is not a feasible solution for a portable app, the main reason is that there are more programs that change registry.
Currently launchers do the same, but only with a few keys that they know the program modifies.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
Actually there is a way that doesn't use drivers.
API hooking.
Implemented already in JauntePE and Thinstall.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
And injecting a DLL into a process, right? Doesn't that need admin privs?
You can inject a dll to most processes created by the same user with SetWindowsHookEx, even as a guest, but that's not the case.
You have all rights to your child processes, so you can inject anything with direct memory manipulation.
You can set hooks with a .dll, it's probably the easiest way, but doing this without is also possible (direct memory manipulation again) and I guess that's the way chosen by Thinstall.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
how they work but, it seems portable versions of apps usually use a launcher that redirects fire transfers and such within a subfolder called App. So I was thinking if it's possible to create a launcher that automatically moves all files to a folder (and subfolders consequently) that's configured the same way as the Registry's folders. (If that makes sense enough) Then it could at least give us portable versions of the apps. The only problem I can foresee is absolute paths but, I'm sure there's a way around that. (As for me I now subst my drive to keep it on K at all times (thanks to gavinborg)).