home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!pageworks.com!world!eff!sol.ctr.columbia.edu!spool.mu.edu!agate!stanford.edu!CSD-NewsHost.Stanford.EDU!Xenon.Stanford.EDU!mrhoten
- From: mrhoten@cs.stanford.edu (Matthew Rhoten)
- Subject: Re: What does 0xB6DB6DB6 mean to you?
- Message-ID: <mrhoten.728238163@Xenon.Stanford.EDU>
- Originator: mrhoten@Xenon.Stanford.EDU
- Sender: news@CSD-NewsHost.Stanford.EDU
- Organization: CS Department, Stanford University, California, USA
- References: <1993Jan28.072816.20649@hobbes.kzoo.edu> <1993Jan28.100231.570@news.unomaha.edu>
- Date: 28 Jan 93 16:22:43 GMT
- Lines: 20
-
- salmon@cwis.unomaha.edu (David Salmon) writes:
-
- >> I would guess it's some kind of debugging tool; the binary
- >> representation is ...110110110110110110... but I can't figure out who
- >> might be reponsible...
-
- >I believe that the code B6DBB6DB... occurrs in unused ROM space.
-
- My impression is that the Mac's initial power-up memory test puts first
- 011011011... and then 101101101... and then 110110110... in memory
- to test it. This would then just be left over from said memory test.
-
- My guess is based on the fact that this is what my old Mac's video
- display looked like during powerup, neh? slowly sliding diagonal bars.
-
- -matt
- --
- Matthew Rhoten | mrhoten@cs.stanford.edu | m_rhoten@leland.stanford.edu
- "When Adam and Eve first saw each other, that's when the blues started."
- -John Lee Hooker
-