dual boot. problem with the evil os.

afrodocter · 12-01-2004, 05:33 PM

thanks for all the help
ive swapped ram before. and disableing mup.sys doesnt help. its the driver after mup.sys ithink.
i wish i new where the config file is for driver loading order then i could figure out which one it is instead of guessing.

i looked at my friends box and alll of them had agp440.sys (or similar ) loading after mup.sys.
i mounted my windows part in linux and moved the agp440.sys to agp440-backup.sys so it wouldnt load.
it froze for a long time in safe mode then it finally booted.
i disabled verifier.
i booted to normal mode.

i would like to learn howto use verifier so i can find the driver and fix it. the microsft docs are not to helpful. does anyone know a good howto, or another method to troubleshoot drivers??

thanks again

afrodocter · 12-02-2004, 08:01 PM

ok
booted up.
removed nvidia drivers. installed then latest nvidia driver. no microsoft signing mesage so i asume it is signed.
started a divx encode and left.
came back to explorer error. i hit close and send error report. i get a blue screen with:
stop c000021a which looks like winlogin error.
i see no way in which this is correlated with my previous problems.

i really want a good way to fix windows driver errors. i know there has to be a method.
anyone?

DeusExLinux · 12-05-2004, 08:34 PM

Easiest fix for windows problems.....

Stop using it.

I don't know the fix to your problem, but I know there are tons of windows forum's where you might be able to find your answers...

Did you build your machine yourself, or did you buy it?

secesh · 12-06-2004, 12:25 AM

i'm still getting a kick out of every time this thread is bumped, that i remember this has nothing to do with linux, and wonder why if you have such problems with some unknown driver you don't:
1) call in one of your 2 supported problems that come with the purchase of XP
or
2) re-install, and pay attention to your system stability as you change things.

i remember my most frustrating support-calls in college (which were virtually all windows machines) were obviously user-caused, and the user had very selective memory about what'd been going on.

not that i'm saying you're to blame...