While you're in there, might as well run the memory diags.
Printable View
While you're in there, might as well run the memory diags.
kk.
this will take me into lunch. will let u know when i get back
This is exactly why I said to run the hard drive manufacturer's diags first. The Dell bios diags are not enough. You could be spending hours trying to fix software when it is actually a hardware problem.
back.
memory test done and pased.
now back to black screen with cursor at upper left.
and to midknyte ... i did create the ubcd and let my pc load it. it's all greek to me.
Just boot to UBCD. Go to HDD - Diagnosis - Then choose the diag that matches your brand of hard drive.
thanks for the direction but unfortunately, dell doesn't say what brand the hd is.
unless spy comes back with some more ideas, i'm going to just reinstall.
i have an irrational boss wanting to know when i'm "going back to work".
Look on the drive, or post what device manager says.
cant get to device manager (system fails to boot) and i have never seen a case like this. have no idea to open it (no screw, etc)
Look in the bios or just open up the case to find the make/model of the drive.
What is the model # of the Dell? If you posted it, I didn't see it.
cant open the case. no screw, no nothing.
it's an dell optiplex 380
how do i look in the bios?
found it.
it's a wd 320gb
doing a "quick test" from ubcd on it
"quick test" completed. no error.
Ok. Continue with the Extended Test.
extended test started.
i leave here in 2 hours. extended test says it will take about 50 minutes.
are we headed anywhere or just grasping at straws?
Verifying the HHD usability. Most important. Like to have $10 for every test showed a bad hdd.
ok, fair enough train.
just saying ... this pc is the one used for accounting, webite interface, all business end of this buiness. it's been out all this week. so i have to balance the time trying to fix it vs the time needed to reintall software and data.
ok ... extended scan done. NO ERROR FOUND.
Ok. Now that you've verified that the hard drive is good, we can proceed with more software fixes.
You mentioned Norton Goback. Did you try restoring from Goback yet?
i just saw this after googling hal.dll:
he corrupted or missing HAL.DLL error message encountered when starting up a Windows operating system is misleading, as the problem comes from inconsistencies in the BOOT.INI file as opposed to the named DLL file. The issue can be solved by editing the boot.ini file manually with the correct partition number. Another way to solve the issue is by rebuilding the Boot.ini file. The computer has to be started with the boot disk to access the boot.ini file. The boot disk for Windows can be downloaded from the internet for free. After Boot.ini has been fixed, the corrupted or missing HAL.DLL error should be fixed.
with "bootcfg /rebuild" done and my pc not letting me "fixboot", how will this be done?
go-back will only go back to start-of-day on monday. when the problem occurred. it won't or can't see anything earlier than that.
ok guys. i leave in 12 minute. take me 2 buses and a subway ride to get home.
and since i was in the ER and an overnight in the hospital earlier this week, i don't have the stamina to stay late tonight.
i'll post my thoughts tonight from home.
What do you mean not letting you fixboot? Did you reboot from the XP cd and run just fixboot from the recovery console? You already ran bootcfg /rebuild, so you don't have to run it again.Quote:
with "bootcfg /rebuild" done and my pc not letting me "fixboot", how will this be done?
Boot from the XP and get to recovery console. Run fixboot.
If that still doesn't work, reboot from the XP and get to recovery console. Run fixmbr.
If that doesn't work, you can try a repair install of XP.
You might want to remove Goback too. It might be hurting more than helping at this point.
That has been a trouble causing programs since I started here at VDR> <shudder>Quote:
You might want to remove Goback too. It might be hurting more than helping at this point.
did both. back to "corrupted or mising hal.dll file"Quote:
Originally Posted by Midknyte
Goback removal:
http://www.wikihow.com/Remove-Norton...the-Hard-Drive
Note that Goback does affect the MBR.
ok. i'll try this.
however, the link after "Download the file" gives me a "no such file or directory"
and the url after "if that link doesn't work" gives me a 404
Hmm. Looks like Norton moved it to a different location:
Try this link:
ftp://ftp.symantec.com/public/englis...ck/NGBBoot.iso
You can try these instructions as well:
http://www.mycrazymachine.com/mcmblog/?p=81
"If you get another prompt to unhook GoBack from the MBR select “YES”. This will take about 1-2 hours to uninstall (?)"
seriously? then god i hope it works. if not i'm going straight to a reinstall of xp.
Either way, you really want to get rid of Goback. Like Train mentioned, it's a nightmare. It's basically a drive overlay. Even if you slave the drive onto another system, you wouldn't be able to see the data.
Once Goback is removed, you can try the fixboot and fixmbr again. If those don't work, try a repair install.
http://pcsupport.about.com/od/operat...txprepair1.htm
sounds like a plan midknyte. thanks.
i'll let u know what happens when i get to work.
i just hope that go-back removal ISN'T 2 hrs. sheesh.
followed the uninstall goback menu.
weird results:
"unhooking goback from mbr
bad command or filename
norton goback has been removed from the partition table
please restart your computer"
it never asked me for the econd (1-2 hr) "unhook" OR (more importantly) the "repair the mbr".
so i restarted and selected the "repair mbr option"
result - hal.dll still missing or corrupt. i assume goback i still there.
went the fixboot and fixmbr routes again just in case (with fingers crossed). no change.
so i'm now doing the repair intall.
will keep you informed.
never got the "repair" option. and the installation disc had trouble with the partition window was on.
was forced to format and completely install
*sigh*
Wow, what an ordeal.
In the long run, a fresh install --without Goback-- should give you a more solid foundation to build on.
However, keep in mind that there will NOT be any more updates from Microsoft for XP, Security or otherwise, after April 8th, 2014, (less than 9 months).
format complete.
install complete.
anti-virus installed and updated.
windows update in process.
this post being done from the "fixed" pc. YAY.
i want to thank all of you for the help you have given me. it's too bad that whatever was wrong with this machine wasn't fixable. and, no, i am NOT reinstalling go-back on it.
<3 to virtualdr and you all.
nice to know.Quote:
Originally Posted by SpywareDr
the reason we haven't updated past XP (all the PCs here came with windows 7 but i also requested XP be installed) is that there are a few critical legacy systems written in qbasic. i have vista at home and i've tried but vista doesn't play well with qbasic. so i'm sure 7 won't.
You're welcome.
i will have to try upgrading to 7 before next spring, but i'll give you all a breather first.Quote:
Originally Posted by zeszut
;)