Please ignore this, it is just information, so if somone searchs they can find it.
Dont ask me:
there is one more HUGE problem a person can have with a p5b deluxe.
i will TRY and explain it, again, i dont UNDERSTAND any of it, but i had this problem, and have a solution to it.
Backup your system before messing with or installing Jmicro raid drivers:
WHen you install the Jmicro raid parts and pieces, a thing called JGOGO.sys CAN (meaning not always) become a filter driver on the INTEL side, when you try and remove the JMICRO , OR JGOGO.sys (manuallly) it is still in the INTEL enumerations for the intel side of the raid driver.
(dont ask me where how or why)
What it dont do:
soo, if you dont have a Sound problem from the atidt.sys, and you still cannot get a good boot from winders (XPpro for me) you cannot boot in safe, or vga, or even net, or even command prompt, Safe isnt safe anymore.
What it dodo:
what you see, when you see the drivers, loading in safe mode, the last thing you see is MUP.exe.. now MUP itself is NEVER the problem when you see it last, it is usually some driver that was trying to load AFTER that.
so a MUP seen last, can be sound drivers, storage (type) drivers, or other first in the sequence of disk type drivers.
you cannot get a boot.log because there is nowhere to store it, its to early, you cant get into safe, because safe includes these things.
your system is basically hosed, but nothing is lost.
so if you had MUP.exe as the last item enumerated on THIS board, then the Jgogo MIGHT be the problem. and there are many ways it could be.
you could have deleted Jgogo.sys, you could have one bad registry entry, you could have attempted a uninstall, and some entry was not included in the uninstall.
the name of THIS particular Jmicro info is js56nen.inf
What you do to fix it:
Well i didnt get that far, i have a backup, and just bring it back in, and fixed it there.
the "fix" (like many of mine) are to tear the parts and pieces out of the registry. the NOT-fix is to delete the drivers Before removing them from the registry.
If you have a way to edit the registry OUTSIDE of the system, then just tear out the parts and pieces, Jraid, Jgogo, and whatever else you can see in the Jmicros INI file.
More thoughts:
it seems that these SCSI (type) drivers are enumerated SOO early, and are so "critical" that you must remove thier existance from the enumerations, as "Safe" modes will still try and fire them up.
it seems that it may have been possible to remove the filter driver from intel, by removing just that part, but i instead removed the whole dang thing, and reinstalled it fresher. V6.10
What do the creaters say:
INTEL does indicate, that thier driver has an ISSUE , in thier latest upgrade , you can see it in the READ-Me , that it can cause problems they havent fixed yet.
i think that it may be the problem, and NOT really thier problem per-say.
how would they know some parasite had attached itself
(filter thing).
Does this mean Jmicro is bad:
Heck no, the jmicro works just fine, whatever they were doing, was all working ok, till I messed with it.
it was totally my fault, and i will do it again
it is just something that if you get its de-instlation out of order, or change drivers without seeing what is there, or lose a file, or something odd and not normal.
if anyone can do something to hoe the system i can so i am NEVER saying that INTEL or JMICRO or thier parts and pieces do not work.
this is just information to help users like me who are screwed.
again, this is ONLY for information, your system is not destroyed, there is nothing wrong with your board, and its just some kind of conflict and driver issue.
Dont ask me:
there is one more HUGE problem a person can have with a p5b deluxe.
i will TRY and explain it, again, i dont UNDERSTAND any of it, but i had this problem, and have a solution to it.
Backup your system before messing with or installing Jmicro raid drivers:
WHen you install the Jmicro raid parts and pieces, a thing called JGOGO.sys CAN (meaning not always) become a filter driver on the INTEL side, when you try and remove the JMICRO , OR JGOGO.sys (manuallly) it is still in the INTEL enumerations for the intel side of the raid driver.
(dont ask me where how or why)
What it dont do:
soo, if you dont have a Sound problem from the atidt.sys, and you still cannot get a good boot from winders (XPpro for me) you cannot boot in safe, or vga, or even net, or even command prompt, Safe isnt safe anymore.
What it dodo:
what you see, when you see the drivers, loading in safe mode, the last thing you see is MUP.exe.. now MUP itself is NEVER the problem when you see it last, it is usually some driver that was trying to load AFTER that.
so a MUP seen last, can be sound drivers, storage (type) drivers, or other first in the sequence of disk type drivers.
you cannot get a boot.log because there is nowhere to store it, its to early, you cant get into safe, because safe includes these things.
your system is basically hosed, but nothing is lost.
so if you had MUP.exe as the last item enumerated on THIS board, then the Jgogo MIGHT be the problem. and there are many ways it could be.
you could have deleted Jgogo.sys, you could have one bad registry entry, you could have attempted a uninstall, and some entry was not included in the uninstall.
the name of THIS particular Jmicro info is js56nen.inf
What you do to fix it:
Well i didnt get that far, i have a backup, and just bring it back in, and fixed it there.
the "fix" (like many of mine) are to tear the parts and pieces out of the registry. the NOT-fix is to delete the drivers Before removing them from the registry.
If you have a way to edit the registry OUTSIDE of the system, then just tear out the parts and pieces, Jraid, Jgogo, and whatever else you can see in the Jmicros INI file.
More thoughts:
it seems that these SCSI (type) drivers are enumerated SOO early, and are so "critical" that you must remove thier existance from the enumerations, as "Safe" modes will still try and fire them up.
it seems that it may have been possible to remove the filter driver from intel, by removing just that part, but i instead removed the whole dang thing, and reinstalled it fresher. V6.10
What do the creaters say:
INTEL does indicate, that thier driver has an ISSUE , in thier latest upgrade , you can see it in the READ-Me , that it can cause problems they havent fixed yet.
i think that it may be the problem, and NOT really thier problem per-say.
how would they know some parasite had attached itself
(filter thing).Does this mean Jmicro is bad:
Heck no, the jmicro works just fine, whatever they were doing, was all working ok, till I messed with it.
it was totally my fault, and i will do it again
it is just something that if you get its de-instlation out of order, or change drivers without seeing what is there, or lose a file, or something odd and not normal.
if anyone can do something to hoe the system i can
so i am NEVER saying that INTEL or JMICRO or thier parts and pieces do not work.this is just information to help users like me who are screwed.
again, this is ONLY for information, your system is not destroyed, there is nothing wrong with your board, and its just some kind of conflict and driver issue.
Last edited:
