Try copying all the project files from the P drive to your local C drive. Then try opening the project.
The problem is likely a slow connection between your computer and the network.
I recommend creating a folder off the root named "Projects". ( C:\Projects ) then for each project, create a folder inside that.
I appreciate the help friend, but I actually tried that already and it didn't work out. I just obtained the Adobe Creative Suite disk so I'm going to try reinstalling, but I'm certain it's more complicated than that.
I think at this point I'm just starting to ponder what would be the best way of proceeding to start a new project and maybe import as much as I can from the old project (styles, topics, images, etc.)
Yeah, if you copied it to a local drive and it's still happening, something is likely messed up with your project itself.
Do you only get error messages with these two files?
Or is it with a bunch of different project level files?
What about .htm files? Does it happen with topic files as well?
If it's just those two files, there may very well be some corruption on those files. You might be able to open each inside of a text editor (I like Notepad++) and see if the xml structure is screwed up. You can probably even run them through an online XML validators such as: XML Validator
Yeah, it's with a bunch of different project files... that was after deleting the .cpd file and trying that. It usually would just keep bringing up different ones until he program froze up (seems it's not hard to do with RH in a large project.) I've already begun with a new project. At least so far, I've been able to import topics, the style sheet I created, etc. so it could be worse.
I'll be giving everyone I know and their dog a backup of this project next time.
Sounds good. That was going to be my next recommendation. Create a new project and start reimporting things a little at a time, backing up with different backups as you go in case something is causing corruption you can roll back to a previous back up if needed.
We have our documentation under source control (we use open source Mercurial) so I can just roll back to an earlier day if things get out of hand. That has saved my bacon a number of times.
A programmer here said the same thing, to get my pc set up for source control - at least that will be helpful in the future. Though I'll likely also be manually creating backups all the time now. Still adding things, but so far so good. So far, it seems that it was either a corruption in the project file or maybe in multiple 'communication' files, such as the .hhp or .hhc ones. Thanks for the help.
My practice has always been to run a backup program that zips my projects
at the end of the day. I prefix the filename with the date in YYMMDD format
and prune from time to time keeping the last in the month and significant
milestones such as a software release.