This content has been marked as final. Show 10 replies
Hi, Karyn. I am so sorry for your troubles. (What I really want to say is "This really sucks!" but I'm too polite to say something like that.)
If your IT guy has seen this before, it's certainly a possibility that RH is doing something. But it seems odd that RH could break file handling on your PC to that extent.
One "baby" question: who installed RoboHelp on your machine? what login ID was the installer using? what security privileges did that login ID have for your machine?
The correct answers are 1) you or the IT guy, 2) yours, 3) admin. If RoboHelp was not installed by the same user who uses it, or if it was installed without admin privileges, it has real problems. You must uninstall RoboHelp and reinstall it with your login and admin privileges. (Your IT guy can stand over your shoulder and take the privileges away again when you're done.)
Yes, it's a pretty basic question, but until a mis-installation of RH is ruled out, you can't really go back to your IT guy and say "It isn't RoboHelp, find something else."
I did the installation myself, logged in as myself, and don't remember what security privileges I had at the time, but figure it must be the usual non-admin user ones. I'll loop back with our IT guy and find out. And if I didn't have Admin privileges at the time, redo the installation with them activated. Will let you know what happens. Cross your fingers that this solves the problem!
Shoot. I just checked and see that the user I was logged in as at the time of installation (myself) is a member of the "administrators" group. So I guess this won't solve the problem. Hmmph.
* IT peeps making you install RH without admin privs.
* IT peeps saying it's OK to use RH on a network.
* IT peeps conducting updates.
* IT peeps installing piece-of-filth source control product.
* IT peeps installing piece-of-filth firewall product.
* IT peeps installing piece-of-filth virus-killing product.
Are you seeing a pattern here? This behavior: "If I try to just open Windows Explorer and extract the image from the offending folder, I can’t – Explorer just freezes up or crashes entirely. " is simply not the result of RH "not play[ing] nicely with other applications."
Hello Karyn -
Shot in the dark - I have had similar problems in the past with other applications and found the problem to be my hard drive going bad... specifically, a number of bad clusters showing up where the directories and files are located on the platter. Try running a diag to test integrity of the media.
Hello Karyn and all,
I thought I'd add my two cents here too, even though I am not sure I am offering the solution to your particular problem.
I have a had a lot of problems with RoboHelp in the past, especially regarding the placement an manipulation of graphics/images. It never rendered other applications useless, but it did cause applications to freeze and on some occassions, crash as well. This was particularly common with PhotoShop and SnagIt.
What i found to have solved my problem (but like I said, yours sounds more severe), is firstly to make sure RH is not saved, working on, etc, a network. That alone fixed most of my problems. I also did an uninstall and reinstall as a last-ditch effort, and the problem has not surfaced since.
I hope you can find and fix your problem!
RoboHelp is not installed on the network so I know that's not the problem (the guy who taught me the program warned me about that). And we've eliminated the admin privileges issue b/c I did have appropriate privileges when I installed.
So that leaves the integrity of the disk as one potential problem and possible interactions with other software such as CVS, anti-virus programs, etc. as another.
My original intent after reading all of these suggestions was to run a diagnosis for the integrity of the disk/media to figure out for sure if the problem was the disk.
But ... my IT guy says he doesn't have time for that. He wants to just start from scratch with a different computer.
So I'm going to reinstall everything - one program at a time - and carefully test along the way to see at what point the problems crop up. And this time, I'm going to do ALL the installations myself, and allow fewer programs to decrease the possibility of interactions (which may or may not be the problem).
If it does turn out to be a program interaction thing, I'll let you guys know. My guess/hope (*fervent hope*) is that the problem will go away.
Thank you all for your suggestions. You've been a tremendous help.
Hello Karyn -
With Windows / Windows apps, starting from scratches is often the best/quickest solution (wish more apps were ported to Linux - don't have that problem).
Pay attention to the order of things...here is how I do it:
- Load Windows
- Call to prove you aren't a thief - do NOT connect to the Internet!
- Load Service Packs (from a CD or Intranet, NOT the Internet!)
- Image the installation
- Load AntiVirus app and updated Definition files (from a CD or Intranet, NOT the Internet!)
- Load MS Office apps
- Load MS Office service packs (from a CD or Intranet, NOT the Internet!)
- Re-image the installation
- Set up and connect to the Internet
- Check/Update antivirus definition files
- Load misc. apps/utilities
- Load misc. updates
- Load RoboHelp
- Call to prove you aren't a thief
- Load RoboHelp update
- Try RH and see what happens
Well, I think I've located the problem and it wasn't RoboHelp. It appears to be a problem with a very old verison of PhotoShop (6.0).
Here's how I figured it out: Got the new laptop (Dell), installed the OS (Windows XP), brought offending (crashing) images over and opened them successfully (tested). Seeing that all was well, I set a restore point - Restore Point #1. Installed FrameMaker 7.1 plus patches, tested, all was fine, then set another restore point - Restore Point #2. Installed RoboHelp X5, tested, and all was fine so set a third restore point and so on and so forth until PhotoShop 6.0, when the problem began again. No sooner had I installed it than attempts to open images crashed PhotoShop. Tried importing the same images in to FrameMaker and Frame crashed. So I used the system restore to roll back one installation and voila! The problem was gone.
So that PhotoShop installation file goes in the trash and we're upgrading.
Hello Karyn -
Good job! I'll keep your fix in my old gray matter...