Re: P75 fishing exploration...... [crime of passion]

Let's play hardball. Suppose that your P75 blithely calls your 1.44 a 360k. Is debug in BASIC?

JWR wrote:
Hi Tim and Tim,

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. . . .

.

Relevant Pages

  • Re: P75 fishing exploration......
    ... 55SX, where the CMOS failed to remember things because of a failing battery, ... Eisenpress) was using debug on the CMOS: ... The method is to boot from a floopy, ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Finding an x86 segment in a BIOS
    ... Patrick Flaherty wrote: ... If you want to find out how to read/write the CMOS the easiest ... If I interpret the results of DEBUG correctly (and if all real-mode x86 opcodes ...
    (comp.lang.asm.x86)
  • Re: P75 fishing exploration...... [crime of passion]
    ... Debug is an external command; part of all versions of DOS. ... I'm not sure if BASIC of this generation does have these commands available ... battery, but didn't initialise correctly when fresh batteries were ... Eisenpress) was using debug on the CMOS: ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Run time error loading web home page
    ... "Ron Badour" wrote: ... exact message I get is -- Run Time error has occurred - do you want to ... This gives the option to debug or not ...
    (microsoft.public.windowsxp.general)
  • Re: Kernel update break access to boot devices?
    ... >> can do with one statement in debug using dos (if you have it ... >> installed) the second you have to remove the cmos battery, ... You're confusing ROM and RAM you can wipe the lower 2k of RAM memory ... simply using debug. ...
    (comp.os.linux.hardware)