Try clearing the CMOS to restore default settings ...


Try clearing the CMOS to restore default settings for memory speed etc.
Check the CMOS battery voltage (I dismantled a machine last night because it was TOTALLY dead, then found the battery was flat).
Check the seating of the graphics card and memory.
Disconnect all the disc drives and any USB devices.
If you have more than one piece of memory, try it one piece at a time (unless 72 pin, where you may need two depending on chipset).





After the 3th pass the prog cold not detec...



After the 3th pass the prog cold not detect an error. I think it is OK.




well thanks for the help. I contacted a toshiba r...


well thanks for the help. I contacted a toshiba repair shop they said 45 for the DMI so im just going to live with 1gig of ram and no card reader.





hbattle wrote:




Hi,
Was trying to get vdpau working, and th...


Hi,
Was trying to get vdpau working, and then I noticed MythWelcome wasn't working so tried to fix that. After turning it off and MythWelcome not appearing to do anything, I powered back on and instead of getting back into myth, I arrived at the initial myth setup page, where I was asked my local host name: localhost, and then after clicking next I was told I could not connect to the db.

I tried to run optimize_mythdb.py (which appears to have replaces optimize_db.sh) and it errored, I manually corrected a number of *.MYI files, though one file (recordedseek.MYI) was objecting to be fixed.
I tried optimize_mythdb.pl again and got this error.




"halt on all errors but keyboard". In th...


"halt on all errors but keyboard". In the same screen where the disk parameters are set.
_________________
edwin/evasive

Do not assume anything

System error, strike any user to continue...




No, apparently the BIOS module named "Notebook" is...


No, apparently the BIOS module named "Notebook" is just the power-management BIOS kernel.

Btw, if I do end up removing some modules - how are they called from the main BIOS portion? Do I need to patch out the calls too, or are BIOS modules simply not called into if they aren't present in AMI BIOS?

I noticed that for the PXE boot-rom, it is listed as a PCI option rom module-type, and the "load address" is not an address, but the 16:16 PCI device-ID code.




yeah, I did that recovery process with the newer S...


yeah, I did that recovery process with the newer September 2003, P17 one that they gave on the website. It seemed to work cause I have the newest version, but it just isn't loading windows and gives me that same stupid error.

Do you mean my boot device priority? Umm... Anyway, my main and only hardrive is C. My floppy is A. My 2 CD-Rom drives are D and E I believe. In bios boot device priority it has 2 drives that are detected. Floppy first, and I think 1 of the CD drives. It detects both CD drives, and a floppy. But, the bios itself doesn't recognize the main hard drive.

You think I should still go ahead and try putting the P16 .bio file into it and switch the jumpers and try loading the old one again? Or is there another way?





oknet wrote:




Yes, hotflashing won't pose a problem. <...


Yes, hotflashing won't pose a problem.
_________________
<betaBIOS> <okBIOS> <Utils> <MyJob>




1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48