Boot Times WTF

[Wile E]

the only object in that tree is:
jmicron jmb36x controller
which im pretty sure is a raid controller

Are you running your sata controller in ide mode in the bios?

 

[ex_reven]

Are you running your sata controller in ide mode in the bios?

i dont have raid if thats what you need to know, but il check anyway

i thought that sata was plug and play just like IDE, and that you only needed to assign it a channel?

 

[Wile E]

I don't have raid either, but I set my bios to AHCI raid mode. By default, it treated the sata hd as an ide drive. Windows also recognized it as an IDE drive. Setting mine to AHCI improved performance for me, but you have to make sure you have your raid drivers installed. Interestingly enough, my sata drive now shows as a 0+1 JBOD raid in the device manager.

 

[ex_reven]

i would call these images interesting
the hard drive is set to IDE just as you said

also, whats that IDE detect timeout?

 

[GLD]

IDK, I would say just go through all of your device manager tree, if you see any thing about commang queuing, uncheck it. Good luck.

 

[Wile E]

Turn that IDE detect crap off. Also set your controller to AHCI if that's an option, RAID if not. Just make sure you have your controller drivers installed in XP first.

 

[ex_reven]

Turn that IDE detect crap off. Also set your controller to AHCI if that's an option, RAID if not. Just make sure you have your controller drivers installed in XP first.

do i need controller drivers for either of them? Or just for raid?

 

[Wile E]

Either. All you have to make sure of is that you installed your chipset drivers, basically.

 

[ex_reven]

it didnt boot on either setting
bsod

probably due to drivers as per my luck, which should be installed because i used a full install when i first used my motherboard cd

...im gonna try alecstars method and see if i can find the source of the error

if that doesnt work, il reinstall the drivers and try again with the raid/ahci setting

...also, when i boot i noticed my ram says its pc5300 and not 6400...wtf? would that be a result of overclocking? i dont see how the bandwidth would go down due to ocing though...

man this is frustrating

 

[ex_reven]

btw thanks for all the help so far Wile E...your always quite dependable man

 

[ex_reven]

gentlemen i believe I have solved my own problem !

Ill let ya know what it was when you wake up

 

[Lazzer408]

I forgot to mention... Clear the prefetch. That sometimes helps. Delete everything in \Windows\Prefetch

 

[Alec§taar]

...im gonna try alecstars method and see if i can find the source of the error

Did browsing thru the EVENT LOGS for ERROR & WARNING messages help you "zero-in" on the 'offending culprit'?

gentlemen i believe I have solved my own problem !

What was the one that was causing the mess??

APK

 

[ex_reven]

Did browsing thru the EVENT LOGS for ERROR & WARNING messages help you "zero-in" on the 'offending culprit'?



What was the one that was causing the mess??

APK

I cleared the event logs and found two errors labelled:
The device, \Device\Scsi\JRAID1, did not respond within the timeout period.

i disregarded this and looked back to the root cause.

Alecstar you probably remember reccomending me to change my settings on my DVD drive to PIO in a previous thread when i said i was encountering a I/O Error when i tried using disks?

While the PIO setting worked, my system encountered problems (the lag issue).
I dunno why, but when the dvd drive is hooked up it lags the system, and while its set to PIO it works but it lags. Disconnecting the drive is the only thing thats fixing the problem.

So ive confirmed that its the dvd drive itself causing the problems, rather than the PIO setting. Maybe i need a new drive

 

[Wile E]

btw thanks for all the help so far Wile E...your always quite dependable man

Thanx reven, it's no problem. When it comes time for a reinstall, you should set up your drive as AHCI in the BIOS, and either use the F6 method to load your Raid drivers during XP setup, or use nLite to build a custom install cd with your raid drivers integrated. You'll probably see a slight performance increase, until then, I wouldn't worry too much. In the meantime, perhaps the new DVD drive isn't such a bad idea. lol

 

[Alec§taar]

I cleared the event logs and found two errors labelled:
The device, \Device\Scsi\JRAID1, did not respond within the timeout period.

i disregarded this and looked back to the root cause.

The EventLog showed you what you needed, to see, yes?

(Gotta watch it w/ SCSI related messages in NT-based OS, because the HAL 'strains them out' as ScSi ("Sexy", lol, NOT Scuzzy) - EVEN IDE/EIDE/SATA... don't let this b.s. throw you, it's just abstractions & filtering driver b.s.)...

Alecstar you probably remember reccomending me to change my settings on my DVD drive to PIO in a previous thread when i said i was encountering a I/O Error when i tried using disks?

Eh, actually, I don't... got a URL, showing that? Because "straight-up" I don't & I'd recall recommending PIO... fact is, I most likely NEVER would, not w/ today's stuff, especially IF you could dedicate 1 device, to IDE/EIDE (which today, imo @ least, is optical disk readers (i.e.-> Cd-Roms/Dvd etc. you know what i mean - too long of a list!)) IF it's designed to handle more than PIO!

If I did? Man... it'd be a "LAST DITCH RESORT"... the hotel I don't want to vacation in, lol!

Honestly on that note... I think you have the wrong guy you're crediting, to be "100% straight up"... I won't take credit, where it's NOT due me, you know??

Personally - I am INTO separating all I/O tasks on ANY kind of disk onto its own separate circuit... even to the point of SSD, especially "only running 512mb of RAM" here... it works for a good deal of stuff, but I separate cables, & NO SLAVES, even w/ today's moderm mobos!

While the PIO setting worked, my system encountered problems (the lag issue).I dunno why, but when the dvd drive is hooked up it lags the system, and while its set to PIO it works but it lags. Disconnecting the drive is the only thing thats fixing the problem.

Put it on its OWN cable... can you DO this? Dedicate the bus it's designed for, to itself... I do this, mainly because I want it to have 1 interrupt to the CPU, as far as optical disks (they are DOG SLOW, by comparison to today's HDD's, any kind, & YOU KNOW THIS, right?)

Put that thing on its own circuit... test it then.

So ive confirmed that its the dvd drive itself causing the problems, rather than the PIO setting. Maybe i need a new drive

Well, glad to have helped, because again?

The EventLog often will tell you, what the heck is up, w/ a LOT of things.. but, this is just something you do, after "all else hardware, fails" because @ certain points, you start realizing something:

THE MACHINE... it's useless, w/ out a GOOD "Ghost in the Machine"...



* IMPORTANT: @ THIS POINT? I would seriously look @ the driverset applied, & IF there is a chipset specific IDE driver (ASUS has this, VIA has this - do you fall under they? IF so... apply THEIR latest to your chipset... it may solve it).

Kid you not... GOOD LUCK!

EDIT PART - IF you have to? UNINSTALL THE S.O.B in devmgmt.msc, reboot, & reinstall, & do use chipset specific drivers (if not before the reboot)...

Why?

Heck -PnP!

Sometimes, it will 'unbury' you, just via simple burn & reinstall, but if you have a chipset specific driverset, especially imo, ASUS &/or VIA - apply them, for burners & optical disks in general... via their IDE/EIDE specific stuff, should this apply to you (I have admittedly NOT read your hardware specs man - sorry)

APK

P.S.=> For what it's worth? IMO, you're looking POSSIBLY @ a Windows Update "burning" a working driver, that is chipset specific, w/ some "Windows Update WHQL stuff" which is stable yes, but many times ONLY PARTIALLY FUNCTIONAL... so, do reapply ANY chipset specific IDE/EIDE drivers... can't hurt, right?

IMO, a chipset specific driver for IDE/EIDE application (or, reapplication, w/ most updated BIOS, hassle - I KNOW!)? Will help, if NOT fix it...

Humor me? Try it... I have this feeling that if you do this? Yea, You'll be cool.... anyhow, later & GOOD luck... apk