Roboform Pro Not Working With v3.30

MikeH · Post by **MikeH** » Wed Sep 03, 2008 9:56 pm

When I upgraded to Sandboxie v3.30, Roboform Pro told me that the trial period had ended and that I had to buy? the program, as I have more than 10 passcards.
I have already bought and activated Roboform Pro.
Did not have this problem when using Sandboxie v3.28.
Have reverted back to Sandboxie v3.28 so that I can use Roboform Pro.

Regards,
Mike

SnDPhoenix · Post by **SnDPhoenix** » Thu Sep 04, 2008 10:28 am

Hmm, this sounds similar to a problem wraithdu had a while ago with an older Sandboxie.
He was trying to use Roboform2go sandboxed and it wouldn't read the license, whereas with me it worked fine.

I can't remember where the thread is or if it was ever resolved though, I am gonna try to find the thread and maybe test it myself.

wraithdu · Post by **wraithdu** » Thu Sep 04, 2008 10:31 am

But this sounds like a problem with Roboform, not RF2Go. I use the installed RF and it works fine. You don't by chance have your sandbox on a different drive than where Roboform is installed do you? RF's licensing works with the drive serial number, so to make a long story short, you have to keep your sandbox on the same drive as your installation. This is why it is a particular problem with RF2Go, since I was using my Sandboxie Portable launcher from a USB stick, and keeping the sandbox on the local HDD for performance reasons.

MikeH · Post by **MikeH** » Thu Sep 04, 2008 11:18 am

wraithdu wrote:You don't by chance have your sandbox on a different drive than where Roboform is installed do you? RF's licensing works with the drive serial number, so to make a long story short, you have to keep your sandbox on the same drive as your installation.

My sandbox is located on my R: drive which is a ramdisk.

Roboform is installed on my C: drive.

This setup works with Sandboxie v3.28 but not with v3.30.

Regards,
Mike

SnDPhoenix · Post by **SnDPhoenix** » Thu Sep 04, 2008 11:25 am

wraithdu wrote:But this sounds like a problem with Roboform, not RF2Go.

Ha, you're right, I read through it fast and thought he meant rf2go.

wraithdu · Post by **wraithdu** » Thu Sep 04, 2008 1:46 pm

Hmm, not sure what the problem is then. I've never had a problem with a local RF install, even when I was trying Sandboxie with a RAMDisk. And I sure don't have any guesses why 3.28 would work and 3.30 would not. Did you try the Resource Monitor for anything strange looking?

MikeH · Post by **MikeH** » Thu Sep 04, 2008 2:13 pm

wraithdu wrote:Did you try the Resource Monitor for anything strange looking?

No I have not.

Thanks for the tip: I'll have a look at it.

Regards,
Mike

MikeH · Post by **MikeH** » Thu Sep 04, 2008 9:14 pm

Resource Access Monitor output:

(Drive) \Device\CdRom0
(Drive) \Device\CdRom1
(Drive) \Device\Floppy0
(Drive) \Device\Harddisk1\DP(1)0-0+6
(Drive) \Device\HarddiskVolume1
(Drive) \Device\HarddiskVolume3
(Drive) \Device\HarddiskVolume4
(Drive) \Device\HarddiskVolumeRD
(Unk) 00000022 \Device\SandboxieDriverApi
(Unk) 00000022 \Device\WMIDataDevice
(Unk) 00000035 \Dfs
(Unk) 00000039 \Device\KsecDD
(Unk) 000000F1 \Device\RasAcd
Clsid -------------------------------
Ipc -------------------------------
Ipc \BaseNamedObjects\{A3BD3259-3E4F-428a-84C8-F0463A9D3EB5}
Ipc \BaseNamedObjects\{A64C7F33-DA35-459b-96CA-63B51FB0CDB9}
Ipc \BaseNamedObjects\ComPlusCOMRegTable
Ipc \BaseNamedObjects\crypt32LogoffEvent
Ipc \BaseNamedObjects\FirefoxStartupMutex
Ipc \BaseNamedObjects\RotHintTable
Ipc \BaseNamedObjects\SbieDllDummyEvent_1264
Ipc \BaseNamedObjects\SbieDllDummyEvent_1356
Ipc \BaseNamedObjects\SbieDllDummyEvent_856
Ipc \BaseNamedObjects\SbieServiceInitComplete_DcomLaunch
Ipc \BaseNamedObjects\SbieServiceInitComplete_RpcSs
Ipc \BaseNamedObjects\ScmCreatedEvent
Ipc \BaseNamedObjects\shell.{210A4BA0-3AEA-1069-A2D9-08002B30309D}
Ipc \BaseNamedObjects\shell.{7CB834F0-527B-11D2-9D1F-0000F805CA57}
Ipc \BaseNamedObjects\shell.{A48F1A32-A340-11D1-BC6B-00A0C90312E1}
Ipc \BaseNamedObjects\userenv: User Profile setup event
Ipc \BaseNamedObjects\ZonesCacheCounterMutex
Ipc \BaseNamedObjects\ZonesCounterMutex
Ipc \BaseNamedObjects\ZonesLockedCacheCounterMutex
Ipc \RPC Control\actkernel
Ipc \RPC Control\epmapper
Ipc \RPC Control\OLEEF1DF8648AE34B469475AE5EEB88
Ipc O \BaseNamedObjects\{45DB34C3-955C-11D3-ABEF-444553540000} Hook
Ipc O \BaseNamedObjects\{45DB34C3-955C-11D3-ABEF-444553540000} Interprocess
Ipc O \BaseNamedObjects\{45DB34C3-955C-11D3-ABEF-444553540000} PrintList
Ipc O \BaseNamedObjects\{45DB34C3-955C-11D3-ABEF-444553540000} SharedData
Ipc O \BaseNamedObjects\{45DB34C3-955C-11D3-ABEF-444553540000} ShellWindowsWatcher
Ipc O \BaseNamedObjects\{45DB34C3-955C-11D3-ABEF-444553540000}U3
Ipc O \BaseNamedObjects\CiceroSharedMemDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.Asm.MutexDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.AsmListCache.FMPDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.Compart.MutexDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.Layouts.MutexDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.LBES.MutexDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.ThreadMarshalInterfaceEvent.000009AC.00000000.00000004
Ipc O \BaseNamedObjects\CTF.ThreadMIConnectionEvent.000009AC.00000000.00000004
Ipc O \BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-329068152-1788223648-1177238915-1004MUTEX.DefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-329068152-1788223648-1177238915-1004SFM.DefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\CTF.TMD.MutexDefaultS-1-5-21-329068152-1788223648-1177238915-1004
Ipc O \BaseNamedObjects\MSCTF.CheckThreadInptIdle.Event.IBF.DNGNB
Ipc O \BaseNamedObjects\MSCTF.CheckThreadInptIdle.Event.IBF.HMINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF..HMINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF.B.GOINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF.C.GOINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF.D.GPINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF.E.GPINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF.F.GPINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.IBF.G.GPINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.MKJ.AB.GPINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.MKJ.BB.GPINB
Ipc O \BaseNamedObjects\MSCTF.MarshalInterface.FileMap.MKJ.P.GPINB
Ipc O \BaseNamedObjects\MSCTF.SendReceive.Event.IBF.IC
Ipc O \BaseNamedObjects\MSCTF.SendReceive.Event.MKJ.IC
Ipc O \BaseNamedObjects\MSCTF.SendReceiveConection.Event.IBF.IC
Ipc O \BaseNamedObjects\MSCTF.SendReceiveConection.Event.MKJ.IC
Ipc O \BaseNamedObjects\MSCTF.Shared.MUTEX.IBF
Ipc O \BaseNamedObjects\MSCTF.Shared.MUTEX.MKJ
Ipc O \BaseNamedObjects\MSCTF.Shared.SFM.IBF
Ipc O \BaseNamedObjects\MSCTF.Shared.SFM.MKJ
Ipc O \BaseNamedObjects\Sandboxie_DeviceIdList
Ipc O \BaseNamedObjects\Sandboxie_DeviceSetupClasses
Ipc O \BaseNamedObjects\ShimCacheMutex
Ipc O \BaseNamedObjects\ShimSharedMemory
Ipc O \KnownDlls\advapi32.dll
Ipc O \KnownDlls\comdlg32.dll
Ipc O \KnownDlls\CRYPT32.dll
Ipc O \KnownDlls\CRYPTUI.dll
Ipc O \KnownDlls\gdi32.dll
Ipc O \KnownDlls\iertutil.dll
Ipc O \KnownDlls\imagehlp.dll
Ipc O \KnownDlls\kernel32.dll
Ipc O \KnownDlls\MSASN1.dll
Ipc O \KnownDlls\msvcrt.dll
Ipc O \KnownDlls\NETAPI32.dll
Ipc O \KnownDlls\Normaliz.dll
Ipc O \KnownDlls\ole32.dll
Ipc O \KnownDlls\oleaut32.dll
Ipc O \KnownDlls\rpcrt4.dll
Ipc O \KnownDlls\Secur32.dll
Ipc O \KnownDlls\SHDOCVW.dll
Ipc O \KnownDlls\shell32.dll
Ipc O \KnownDlls\SHLWAPI.dll
Ipc O \KnownDlls\urlmon.dll
Ipc O \KnownDlls\user32.dll
Ipc O \KnownDlls\USERENV.dll
Ipc O \KnownDlls\version.dll
Ipc O \KnownDlls\wininet.dll
Ipc O \KnownDlls\WINTRUST.dll
Ipc O \KnownDlls\wldap32.dll
Ipc O \LsaAuthenticationPort
Ipc O \NLS\NlsSectionCType
Ipc O \NLS\NlsSectionLocale
Ipc O \NLS\NlsSectionSortkey
Ipc O \NLS\NlsSectionSortTbls
Ipc O \NLS\NlsSectionUnicode
Ipc O \RPC Control\DNSResolver
Ipc O \RPC Control\SbieSvcPort
Ipc O \Security\LSA_AUTHENTICATION_INITIALIZED
Ipc O \ThemeApiPort
Ipc O \Windows\ApiPort
Pipe -------------------------------
Pipe O \Device\Afd
Pipe O \Device\Afd\AsyncConnectHlp
Pipe O \Device\Afd\Endpoint
Pipe O \Device\NamedPipe\ShimViewer
Pipe X \Device\NamedPipe\lsarpc
WinCls -------------------------------
WinCls MozillaWindowClass
WinCls O CicLoaderWndClass
WinCls O CicMarshalWndClass
WinCls O Shell_TrayWnd
WinCls X DDEMLMom
WinCls X FirefoxMessageWindow
WinCls X Progman

Does anyone have any ideas?

Regards,
Mike

tzuk · Post by **tzuk** » Fri Sep 05, 2008 9:56 am

MikeH, as an experiment, reconfigure Sandboxie to put your sandbox on the same drive as the installation of RoboForm, namely drive C.

MikeH · Post by **MikeH** » Fri Sep 05, 2008 11:35 am

tzuk wrote:MikeH, as an experiment, reconfigure Sandboxie to put your sandbox on the same drive as the installation of RoboForm, namely drive C.

Setting the container folder to the default location on the C drive allows me to use Roboform Pro in a normal fashion: that is to say I do not get the popup that says the trial period has expired and that I must either buy or activate Roboform Pro whenever I use it to log into a website.

Regards,
Mike

HarryStottle · Post by **HarryStottle** » Fri Sep 05, 2008 3:01 pm

For what it's worth, I had a similar problem (which last hit me about 5 days ago). The first time it happened was in my first week of using EazFix and I assumed it was a failure caused by one of its restores being somehow minced. I wrote to RF to ask what files would have to be damaged or misplaced in order for the activation status to be lost and there reply was:

Roboform keeps its activation data and the path to the User Data folder in Registry - so if your utility altered the Registry or changed some keys - that is the reason why Roboform "forgot" the path to the User Data folder and lost the activation status.

Sandboxie, of course, does play with the Registry Hive so anything is possible. In any case, I simply reactivated - which, apparently, you can do as many times as you like! (I've since re-activated about 6 times) - by going to the activation site and re-entering your username and registered email address.

I'm also using my sandbox and roboform data on different drives, so I might try relocating to see if that makes any difference (though given the triviality of re-activation, it isn't a priority)

wraithdu · Post by **wraithdu** » Fri Sep 05, 2008 3:56 pm

As I explained above, it's because RF uses the physical drive's serial number as part of the activation...meaning it's activated on that physical drive only. When the sandbox is on another drive, RF gets confused about the drive serial number and deactivates itself. You could re-activate once running in the sandbox and it should work ok, but you'll have to re-activate every time you empty the sandbox after that. Constantly re-activating will eventually throw up some red flags on your serial number.

Workarounds -
1. Keep the sandbox on the same physical drive as RF.
2. Change the drive serial number on your sandbox drive to match the serial number where RF is installed** I don't know what other consequences this might have.
3. Keep your sandbox on a TrueCrypt mounted volume (or similar virtual drive) and change the serial number of that mounted drive to match the drive where RF is installed.

I tried all sorts of open paths and such when I was messing around with RF2Go. The above were the best solutions I came up with.

Guest · Post by **Guest** » Fri Sep 05, 2008 6:55 pm

wraithdu wrote:1. Keep the sandbox on the same physical drive as RF.

that's the one I'm going to try first. But can't actually find a setting or config item where we can set a new sandbox folder location and looking in the online manual for "sandbox folder" or "sandbox location" came up with zilch, so would appreciate the heads up on how to change that...

SnDPhoenix · Post by **SnDPhoenix** » Fri Sep 05, 2008 7:00 pm

Anonymous wrote:
wraithdu wrote:1. Keep the sandbox on the same physical drive as RF.
that's the one I'm going to try first. But can't actually find a setting or config item where we can set a new sandbox folder location and looking in the online manual for "sandbox folder" or "sandbox location" came up with zilch, so would appreciate the heads up on how to change that...

Haha, thats cause it is referred to as the "Container" folder instead.

Anyways, just open Sandboxie Control and then click "Sandbox -> Set container folder", then you can change the location of the sandbox folder.

Guest · Post by **Guest** » Sat Sep 06, 2008 12:37 pm

SnDPhoenix wrote:Haha, thats cause it is referred to as the "Container" folder instead.

Anyways, just open Sandboxie Control and then click "Sandbox -> Set container folder", then you can change the location of the sandbox folder.

Sorted. Thanks

Sandboxie Support

Roboform Pro Not Working With v3.30

Roboform Pro Not Working With v3.30

Who is online