Re: P75 fishing exploration......

Hi Tim and Tim,

"Tim Clarke" <tc_in_guildford@xxxxxxxx> schreef in bericht
news:8x2Nf.61126$mf2.26850@xxxxxxxxxxxxxxxxxxxxxxx
"Tim Knight/CT" <msgtknight@xxxxxxxxx> wrote in message
news:1141145586.093148.53510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
No adapters installed...........

Turn on machine without a refdisk...........

1. After 20 seconds, the screen blinks lightly about 3 times and then
turns bright........
(excellent raster)

2. Memory counts to 16000 kb very slowly........

3. Floppy drive cycles......beep-beep.........221 then 162/163

With these POST error codes the next step ought to be to fix those by
inserting the RefDisk before pressing F1. If it doesn't boot into the
System
Programs then suspect the FDD and/or related RTC/CMOS settings preventing
the RefDisk being read correctly.

This is a bit of a long shot, but could this be a similar problem to the
55SX, where the CMOS failed to remember things because of a failing battery,
but didn't initialise correctly when fresh batteries were installed? (see
the thread "55sx wants to live").
The thing that helped (according to Mark Dodel referring to Aaron
Eisenpress) was using debug on the CMOS:
===quote===
"I did some searching on the 55sx problem after replacing the Dallas
RTC chip, and found one suggestion that says you need to clear the
CMOS before the configuration will take.

The method is to boot from a floopy (left in the typo for originality, Ed),
run DEBUG, and type

o 70 13
o 71 00
q

Then run the reference diskette and autoconfigure again.""

===quote===
Now I don't now about the interchangeability of debug commands between these
two computers; maybe some others in this group can shed some light on this,
with their knowledge of CMOSses?



From Peter W's site:

221 0002 21XX ROM to RAM parity error
1. System Board

162 0001 62XX Be sure all devices are powered-on. Check Enable/Disable
settings.Configuration changed ? If so, run Automatic Configuration.
1. Any Device
2. Battery

163 0001 63XX Date and time error
1. Set Date and Time

Can't do much more now, as I've got to pack and make final arrangements
for
my trip. But it does seem that the lack of the possibility to boot to the
RefDisk (a "Catch-22" problem) is the primary issue.

I'll try to remember to follow-up on this later or when I get back.
--
Regards,
Tim Clarke (a.k.a. WBST)
Guildford, U.K.


BTW CT: the CD is in, thanks! And in full-color, *wow*!
Now to find time and a space to set up the M77 and install the demo. . . .

--
Jelte

Reply? Remove CAPS from address.


.

Relevant Pages

  • Re: Resetting BIOS to factory defaults when you donīt have access to i
    ... boot devices and box itself. ... My BIOS is now inaccessible. ... Turn the computer on Without the Battery. ... Windows still booted so I tried A) B), or removing the CMOS battery. ...
    (microsoft.public.windowsxp.general)
  • Re: [F9] laptop not booting - reinstall MBR?
    ... ordinarily get to the "Hit Enter for options" boot screen, ... If it were me I would start by re-booting - loading the factory CMOS ... the old CMOS battery or dirty CMOS battery connector. ... look at the actual MBR and probaby first sector. ...
    (Fedora)
  • RE: CMOS jumpers
    ... You may need a new CMOS Battery, also you can access the BIOS by Tapping F2 ... Can you still Boot into safe Mode?. ... "attilathehun1" wrote: ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Bios will not initialize my video
    ... You could try to 'reset' by shorting the clear cmos jumper with the rig ... > My computer will not initialize the video on Bios boot-up. ... > I know that I need to replace my CMOS battery because if I cold boot my ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: P75 fishing exploration...... [crime of passion]
    ... 55SX, where the CMOS failed to remember things because of a failing battery, but didn't initialise correctly when fresh batteries were installed? ... The thing that helped was using debug on the CMOS: ... 163 0001 63XX Date and time error ...
    (comp.sys.ibm.ps2.hardware)