PC technical problem (not SS related)

Welcome, Guest. Please login or register.

[Stuart2007]

Any ideas on this will be appreciated.

I have a piece of software that keeps dumping me out at the title page. The people who wrote the software can't work it out (!). I had a power failure when I tried to boot up. I've tried to re-install it several times as well as try the repair function.

What I need is a programme that will sit on the desktop and notify me- in real time- what processes are being activated at that time; so that I can see which process it is crashing out on. (It used to be very, very simple on the Amiga) Does anyone know of such a programme?

Case of Marmite for the winner of the ideas competition 

[TerryRussell]

You can start Windows with a Bootlog function.

Set the program to start as a process on start up (via the System/Administrative tools/Services menu).

Reboot the PC and keep stabbing the F6 key (with a finger, not a metal object). Eventually a menu will come up and ask why you are disturbing Windows etc. You should then be able to press F8 and switch to the boot menu options. Tell Windows to start with Bootlog. Then, when the PC has started up, you can take a look at the Bootlog and see which start-up process have failed.

Some programs are badly behaved and don't get recorded in the Bootlog, but the majory will do.

PS you might want to open a command prompt and type

chkdsk c: /f

After Windows has stopped moaning about not being able to do it right now, because it is talking to its Mother, reboot the PC and let it check your disk. You never know, the program might then work...

[Stuart2007]

Thanks Terry. But it isn't a problem that's happening whilst booting. Although the basic, simple log is what I need to monitor what process it's crashing on.

I've tried 2 from MS but they are listing literally 100,000s of file processes which it is impossible (for me) to monitor.

The hard drive might well be stuffed, but I don't think that's what is causing THIS problem  


EDIT: Sorted. THanks for the advice Terry. It turned out to be a couple of dodgy DLLs. Well, Marmite all round then... 

[TerryRussell]