Newbies Phable Posted July 16, 2004 Newbies Posted July 16, 2004 I am running FMPro 5 on Windows 98. It was running fine before, but for the last month or so it has been taking almost 15 minutes to load up. Once it's loaded, it works fine. The only thing I can think that changed is the IT guy removed a virus from my computer shortly before the slow startup started. I'm running out of ideas, and it's annoying to start it up in the morning, get coffee, and then have to leave it running all day. Thanks for any and all help!
DanBrill Posted July 16, 2004 Posted July 16, 2004 Hi Phable, Welcome to the Forum. Your situation -- outside of the coffee -- sounds awful. Is it just on one machine, or is this on a network. Is it FileMaker alone taking this long, or is it your set of files that takes this long to load? Or are you opening your fp5 files directly and having FM open by association? The first thing I'd try is uninstalling FM and reinstalling it. Good luck, Dan
Newbies Phable Posted July 16, 2004 Author Newbies Posted July 16, 2004 Dan, thanks for the quick reply. My first instinct was network as well. However, I have another workstation on the same node using the same file set that loads up like normal. My first step was re-install, but I still have the same result. I'm not sure what else could be wrong. I don't know what kind of setting in the operating system could cause this kind of a slow down. Thankfully the coffee is good and fresh -Phable
-Queue- Posted July 16, 2004 Posted July 16, 2004 Delete all temp files. When FM crashes, it doesn't remove old ones, and it seems to go through all of the old ones before allowing itself to start. After a while this can lead to one heck of a startup wait time.
Steve T. Posted July 16, 2004 Posted July 16, 2004 You're using Windows, but if it were a Mac, I'd also recommend deleting preference files. For example, a Mac can spend too long searching for something it thinks is the default (like a network protocol) and tries and tries and tries and tries for too long a period before giving up and then trying something else which works immediately. Maybe it's something like that... you're terminal might be searching for something or waiting for something and taking too long before moving on. Hmm... I guess that's what Queue basically said, too. Good luck! --ST
Recommended Posts
This topic is 7704 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now