ITPython

Member
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ITPython

  • Rank
    Member
  1. So any progress? I have 2 days until my OA license expires, if this problem cannot be resolved then there is no reason for me to keep a subscription.
  2. Yeah that is my thread (which I'm sure you know ). The problems I am having aren't from OA being installed on both boots, it's simply a software glitch with V5, which for some reason doesn't agree with my second boot (works perfectly fine on my main boot though). But rest assured it has nothing to do with the fact that I have OA installed on both boots. In fact my brother had a very similar problem with V5 on his computer as well, and he only boots a single OS. V5 simply has some major flaws that need to be fixed. You may end up having problems with what you are trying to do, but it won't be from OA installs on both boots.
  3. I also dual-boot XP (but with partitions instead of separate disks), and yes you can install OA in the same default folder for each boot. Just think about the situation, each of your XP installations are on separate disks and run independently from each other, and each installation you do within XP is tied to whatever disk/boot you are currently using. There is no 'contamination' occurring when you do installations within a XP boot unless there is issues with the drive letters changing or something. Essentially each XP boot you use is like using an entirely different computer, the only "settings" that are shared between them is the boot loader and MBR. And while the computer is capable of accessing the disks no matter what boot you are on, I have never had any cross contamination issues with installations and I have been dual-booting for several years now. Just make sure you pick the right drive to clone to/from, because you wouldn't want to clone over the disk responsible for handling the boot process. Easy way to know which disk has the boot loader is to go into the main C drive and see if there is a ntldr and a boot.ini file. Whatever disk has those files, handles the boot. So you don't want to erase that disk (which a disk image clone would do).
  4. Ok,I got some downtime to relay some more troubleshooting info. Mostly bad news, but some potentially good news as well. Andrey, you wanted me to try rebooting twice after a uninstall, so that is what I decided to do, this time I penciled down the steps so I could remember exactly what I did and in what order. 1. Uninstalled V4.0.0.45 which was currently working fine. Rebooted twice after uninstalling. 2. Began V5 (1097 build) install. 3. Entered license key 4. Installed into a new folder 5. Install complete. Began safety check wizard 6. For less potential issues, I chose the option "Trust everything on this computer" 7. After safety check ran and when prompted to change/customize OA settings, I did not change any settings. 8. OA prompts me to restart computer. 9. Restart computer, OA starts up in learning mode. Same issues as before, nothing loads except for OA. 10. After learning mode finished, I figured I could reboot twice just for the heck of it. 11. After rebooting twice the problem was still occurring. No changes. 12. Now I decide to troubleshoot further. 13. I close and shutdown OA from the tray with the right-click context menu. 14. I go into my start menu and click on OA. Nothing happens and a minuet or so later I get an error saying OA could not be started. 15. After the failed start I proceed to my services to manually start OA and OAhelper 16. After starting both services (which were on automatic) I once again went to my start menu and started OA. 17. This time OA started. 18. After this I noticed that OA was now allowing me to use my computer normally, meaning I could start/run programs, just like normal. 19. I decided to try my luck and reboot, hoping these new changes would carry on with the next reboot. 20. To my surprise after the reboot, my programs and everything else started up like normal. I was very happy! 21. Now that it seemed everything was working properly I decided to customize the OA settings how I normally like them. IE running certain programs as run safer, blocking certain programs from accessing the net etc etc. 22. After setting the OA settings just how I like them, I decided to to see if it would work after another reboot. 23. After rebooting everything started as normal, and everything seemed normal. Very good! 24. I go back into the OA settings to see if everything was still working properly. This is when I saw the first problem. My firewall rules had been reset. I had set lsass.exe and System to be blocked from internet access (red), but after the restart they were no longer blocked but in fact allowed (green.) 25. Wondering what the deal was I tried blocking them again and rebooted to see if the rules would stick. After the reboot they had reset once again. I had them blocked, and they were no longer blocked after the restart. The only blocks that stayed were the RAW and ICMP blocks, but the entire program was still allowed. Note that the programs that had a OA pop-up prompt, stayed blocked. But my manual lsass.exe and System blocks did not stick. 26. After noticing this issue I started to think there was a major bug going on, and that is when I noticed that my Web Shield had been turned off, and I could not turn it on. I had sort of noticed it was disabled back on step 18, but I ignored it since I figured it would reset back to normal after a reboot. So after all that I got fed up with V5 and tried to install V4.0.0.45 using the upgrade method I had used previously in order to get my license onto 4.0.0.45 (which avoided the 10054 issue). However there was no upgrade option... and after 4 more hours of installing/uninstalling/troubleshooting I finally managed to get the option to upgrade from v5 to v4.0.0.45, and that is where I stand right now. So there you have it, another adventure of stress and frustration with V5. I can say right now, unless there is a sure fire fix for this, I am NOT going to troubleshoot v5 anymore, because I was extremely lucky to get 4.0.0.45 back working again. And I do not want to go through that again. Hopefully this new info helps somebody, because this is one heck of a problem. And yes Andrey, OAhelper was running with V5.
  5. You seem to be confused as to how dual-booting OS's works. Both my XP boots are completely independent of each other, and I am NOT installing OA in the same folder as the OA on my main boot. My SSD is partitioned, and each XP boot installs programs and performs operations separately from each other, and each XP partition have their own drive letters as well. You also seem to have trouble reading my replies, because I stated in my last post that I already tried installing into another folder which did NOT work. In the future if you could actually read my post before replying, that would be greatly appreciated. Because arrogance and customer service do not go well together. However, for the sake of further troubleshooting I will try the whole process over again, except this time reboot twice after the uninstall. I will report back with my findings. BTW I was talking to my brother today, who I have always recommended OA to, and he also had a ton of problems installing V5 on his computer. Very similar to the problems I am having, only his problems were much worse. They were similar in the fact that OA was the only thing that worked, while the rest of the computer was inaccessible while OA was running. So something is seriously wrong with V5, and I hope we can get to the bottom of this.
  6. Aside from rebooting twice after a uninstall, I already tried that in one of my many efforts to troubleshoot the problem. In the past I remember that helping with one of my older OA versions, installing to a different folder. But it did no good when I tried that with V5. Now I could try the double reboot + using a new folder, but it seems the biggest chance for success would have been installing into another folder. But if a double reboot really makes a huge difference I can uninstall my currently working 4.0.0.45 to give it a try.
  7. --- Continued --- I never thought about rebooting twice after a uninstall, I only rebooted when the installation/uninstall told me to do so. However in one of my attempts to figure out the problem, I used Revo uninstaller to completely get rid of anything OA related (registry stuff too). And even then a fresh install did not work. So even with the lack of config files altogether, the problem still occurred. Everything is the same (security software wise) except my AV. On my main boot I am using Avira Premium, whereas on my second boot I am using GDATA. I have yet to have any license problems, as I am always able to register the license with V5 just fine. It is V4.0.0.45 that has this notorious socket error problem, but this is due to the older version of OA. Because even if I can't register the key with v4 (due to the 10054 socket error) I can uninstall v4 then register the key with v5 during its installation. As mentioned above, the license key is not the problem. The amount of times I re-registered my key I would have had to buy a 200-PC license if each one was considered "a new key". Not sure what you are getting at here, the license key I have used is the same across my entire PC regardless of what version I am using. Well it's the only way I can actually get 4.0.0.45 activated with my key, otherwise I just get the socket error problem and can't ever use my old OA version. So far I haven't encountered any stability problems or bugs with 4.0.0.45 when I did the upgrade from v5. Unless using an old key renders my computer useless as described in my situation, I don't know why you are even bringing up the license key as a topic. It is a moot point and irrelevant to my main problem. If I knew that there was going to be so many problems with v5 on my second boot I would have tried to document every step I took, but as it stands trying to re-write everything I did is like trying to describe a car accident after it is over. I spent hours upon hours troubleshooting, trying every technique and solution I knew, so I hope you can understand that since I do not have a photographic memory I cannot describe every single step I took. Either way I described the situation perfectly fine in the OP and proceeding posts, as most of the follow-up questions you asked above were completely irrelevant to the actual problem.
  8. Ok, I started logging on my main XP boot (which has no problem with V5), restarted, then sent the logs to the email address above with a link to this thread. Sorry for taking a while to respond, I wasn't expecting a reply so soon. No, only my second XP boot started with v4.0.0.45, my main XP boot got upgraded to OA V5 from OA v4.5 Irrelevant IMO, but I believe I have a 3-PC single license OA subscription. I use the same license key with both OA's. On my main boot I did a upgrade install to V5. Never imported. --- Continued on next post due to quote limitations ---
  9. Andrew, Thanks for the reply. What exactly do you want me to do with the logs on my main XP boot? (which has no problems whatsoever with OA V5). Do you just want me to turn on a logging, do a little bit of normal computer stuff then send the logs to you? Cause I already sent you guys logs from my second XP boot in which the problems occur at. And as stated above, I managed to get 4.0.0.45 installed and working on my second boot and would rather not go back to the broken V5 until some solution is made. If you need extra logs from a V5 installation on my second boot I will do it, but please find the logs I already sent you and then let me know what else you need.
  10. They are both on the same disk, using the standard Windows boot manager. I have been dual booting XP for years now and never had any problems with OA on either of the boots until V5. If you have any suggestions or solutions, please reply to the thread I created in the OA section. http://support.emsisoft.com/topic/4954-oa-renders-my-second-xp-boot-useless/ @cat - I suppose I could try a more direct line of customer support, but I have always found the forums for OA to do the trick, but I guess Emsisoft doesn't read or participate in their forums as much as Tall Emu did.
  11. I too am disappointed with the support here, I cannot even install OA V5 on my second XP boot otherwise it renders that boot completely useless. I have provided logs and detailed information to Emsisoft about this, yet nobody has gotten back to me with a solution or even to tell me they are working on it. I have also been a paying customer for several years as well, and I doubt they are even giving my issue a second thought. Even though it is a MAJOR problem that cripples my second XP boot. This is usually what happens when one company sells out to another, customer service degrades drastically and the product eventually suffers and dies a slow death. Tall Emu was wonderful with service and support, Emsisoft just doesn't seem to be as vigilant in helping their customers. I absolutely love OA and cannot even imagine using anything else, but I may have to consider choosing something else as my subscription ends soon, and I am not sure i want to bother buying another if they won't help me with the OA problems I have been having.
  12. I noticed this as well when I was recently trying to troubleshoot a problem with a V5 install on my computer. When I tried to do the 30-day trial I ended up getting the free version instead.
  13. Well I have managed to temporarily fix the problem, and by that I mean I was able to get 4.0.0.45 back up and running. Originally when I tried to install 4.0.0.45 I would get the infamous "10054 Socket error" which would prevent me from registering my key and thus making it so OA would not run. However I found that if I installed V5, registered my key, then do an "upgrade" install to 4.0.0.45, I was able to bypass the key authoring system since my key was already authorized from the V5 install. I'm just glad there was a upgrade option when going from a higher version to a lower one, otherwise my second XP boot would have been completely useless until somebody at OA fixed the problem. On that note I haven't heard back from anybody at OA and obviously nobody has responded here, which is disappointing. If I did not have a working XP boot and was unable to use my computer, I would be incredibly ticked off at the lack of help from the OA team on this, as it has been a few days since I reported this. I don't know about the rest of you, but even a day without my computer is far too long. I'm just lucky I have two XP boots and that one of them was working properly. I will keep checking this topic and/or waiting for a email from the OA team, because my premium subscription is ending soon, and I want to upgrade to the latest version of OA before I cannot upgrade anymore. BTW to any OA/Emsisoft staff reading this, I realize the email I used for this forum account and the email I used to send the OA logs does not match my email from when I purchased OA, but don't think I am lying about owning a subscription because you cannot find my email associated with any purchases. I use email aliases to help protect my identify on the net, so if you want to know my true email that is linked to my original OA purchase, let me know by PM or by simply responding to my OA log email. I am a active subscriber and I hope I am not shrugged off as some kind of freeloader expecting priority customer service, as I am a paying customer and have been for several years. I might consider re-doing my subscription, however if the service is lacking I really wouldn't want to pay for that now would I?
  14. Alright, I got the logs sent off. I tried to start various programs and actually managed to get a few things going, like Internet Explore and my forced Firefox sandbox. Although my default firefox sandbox still would not start up. Another interesting thing to note is that when I added GDATA to the exclusions list and restarted my computer, the GDATA tray icon showed up and I was able to start it up. And also note that several of my normal programs (like GDATA, Sandboxie and their related processes) are all present in the process list of task manager, but I just cannot start them up into a GUI.
  15. I did mention my security software at the top of the thread next to what version of windows I have and what version OA I am using. But thanks for the reply stapp, I will log back into my second XP boot and gather up the logs to email. Will they reply back or am I just to assume the problem will be eventually worked out in some future update? Because I need to get my second boot up and running soon with a properly working OA.