0101010101 at boot

[Rodolphe POLLET]

Hello everybody,

I'm in serious trouble. I used to have Linux on hda (on a WD HD) and everything was fine. Then somebody asked me to put W9
5 so i bought an IBM HD.
I decided first to put W95 alone on hda and CDROM on hdb. After i installed W95, at reboot, i saw 010101001... on the scre
en, printing infinitly.
Thinking that it was a problem with my IBM HD, i changed it for a new one (a Seagate). Everything seemed to work so i brou
ght back Linux and my new configuration was :
_ W95 on hda
_ CDROM on hdb
_ Linux on hdc
The two OS were perfectly working when after a few hours, the same strange thing occured : 010101001... on my whole screen
. I wonder if it is a VIRUS or if i did a mistake manipulating the inside of my PC ?

Please help me.

[John Wolanski]

I can't help you, but I doubt it's a virus. I've had the same thing
happen to me. I think it has something to do with the master boot
record of the HDD and LILO, but I'm not sure.

--
-John Wolanski
Remove the "_removethis" from my email address to reply.

[Eggert Ehmke]

On 14 Dec 1998 09:01:19 GMT, pol...@liliput.lct.jussieu.fr (Rodolphe POLLET)
wrote:

>Hello everybody,

>
>I'm in serious trouble. I used to have Linux on hda (on a WD HD) and everything was fine. Then somebody asked me to put W9
>5 so i bought an IBM HD.
>I decided first to put W95 alone on hda and CDROM on hdb. After i installed W95, at reboot, i saw 010101001... on the scre
>en, printing infinitly.
>Thinking that it was a problem with my IBM HD, i changed it for a new one (a Seagate). Everything seemed to work so i brou
>ght back Linux and my new configuration was :
> _ W95 on hda
> _ CDROM on hdb
> _ Linux on hdc
>The two OS were perfectly working when after a few hours, the same strange thing occured : 010101001... on my whole screen
>. I wonder if it is a VIRUS or if i did a mistake manipulating the inside of my PC ?
>

Look into MAN LILO or lilohelp.txt, somewhere at the end some binary output is
referred. Something about your boot configuration might be faulty. Can't tell
the exact location cause sitting at my NT workstation now ...

-----------------------------------------------------
mailto: Eggert...@bln.siemens.de
-----------------------------------------------------

[Derek Milliner]

Ahh, what timing... I've just hit the same problem. I'm pretty certain this is something to do with LILO. I have SuSE 5.2
installed on a separate 2.4GB disk in my PC. The first time I got this was with Win95 on my C drive. I thought the hardware
was busted, so used my (W95) boot diskette to fire up the system, low-level formatted the C drive and installed Win98. All was
fine until I rebuilt the Linux kernel (I wanted sound support; sorry, but I really can't live without music while I work :-).
After being a good chap and running the LILO bit as suggested, I'm back to 01 01 01 01...

Not being a Linux user for long (2 weeks), and been very used to being cuddled by IBM's AIX environment (system
administrator's heaven, but plenty to keep the hacker in me satisfied), I'm a little concerned. I noticed something in an
earlier posting about using fdisk /mbr to reinstate the MBR as windows likes it. I'll try it out this evening when I get home
(and the kids are in bed etc...) - if it works I'll post a confirmation.

Del.

Rodolphe POLLET wrote:

> Hello everybody,
>
> I'm in serious trouble. I used to have Linux on hda (on a WD HD) and everything was fine. Then somebody asked me to put W9
> 5 so i bought an IBM HD.
> I decided first to put W95 alone on hda and CDROM on hdb. After i installed W95, at reboot, i saw 010101001... on the scre
> en, printing infinitly.
> Thinking that it was a problem with my IBM HD, i changed it for a new one (a Seagate). Everything seemed to work so i brou
> ght back Linux and my new configuration was :
> _ W95 on hda
> _ CDROM on hdb
> _ Linux on hdc
> The two OS were perfectly working when after a few hours, the same strange thing occured : 010101001... on my whole screen
> . I wonder if it is a VIRUS or if i did a mistake manipulating the inside of my PC ?
>

> Please help me.

[Del]

As promised, here's the confirmation. I booted my PC from the W95 diskette,
typed 'fdisk /mbr' (not a self-documented command) and here I am, using W98
/ Outlook to post this note. Now all I gotta do is get Linux sorted out
PPP-wise so's I can post from there instead. Next stop StarOffice 5,
Wordperfect 8 and just maybe I can get away from the world of Microshaft at
last...

Del.

Derek Milliner wrote in message <3675C453...@anix.co.uk>...

>Ahh, what timing... I've just hit the same problem. I'm pretty certain this
is something to do with LILO. I have SuSE 5.2

[snip]

>earlier posting about using fdisk /mbr to reinstate the MBR as windows
likes it. I'll try it out this evening when I get home
>(and the kids are in bed etc...) - if it works I'll post a confirmation.
>
>Del.

[snip]

[49b...@gmail.com]

On Monday, December 14, 1998 3:00:00 AM UTC-5, Rodolphe POLLET wrote:
> Hello everybody,
>
> I'm in serious trouble. I used to have Linux on hda (on a WD HD) and everything was fine. Then somebody asked me to put W9
> 5 so i bought an IBM HD.
> I decided first to put W95 alone on hda and CDROM on hdb. After i installed W95, at reboot, i saw 010101001... on the scre
> en, printing infinitly.
> Thinking that it was a problem with my IBM HD, i changed it for a new one (a Seagate). Everything seemed to work so i brou

> ght back Linux and my new configuration was :bill gates screen of death what a ass hole is what it was

[Bobbie Sellers]

Keep reading 1998 and 1999 and I am sure you will find that Rodolphe
got his help.
W95 = GEOS for the Apple ][ or C+64

bliss

[William Unruh]

That looks like you were running lilo as the boot manager, and it got
messed up (eg the /boot directory and the vmlinuz file became
inaccessible). You have not given us enough information.

a) Why in the world would you put win 95 on the system? It is old and
highly insecure.
cdrom on hdb? It sounds like you have a very old computer with the old
ATA disk interface, rather than SATA.
b) What boot manager are you running? lilo? grub? grub2?
c) How old is your system? some older bioses cannot see past 4GB on a
disk so cannot boot if the /boot/vmlinuz is higher than that on the
disk.

Ie, more information will get you better advice.

[William Unruh]

Oops sorry, did not see the date. How in the world are such ancient
posts being resurected?

>
> bliss

[The Natural Philosopher]

Google is God in this instance

>>
>> bliss


--
Ineptocracy

(in-ep-toc’-ra-cy) – a system of government where the least capable to
lead are elected by the least capable of producing, and where the
members of society least likely to sustain themselves or succeed, are
rewarded with goods and services paid for by the confiscated wealth of a
diminishing number of producers.

[Aragorn]

On Tuesday 08 July 2014 23:21, William Unruh conveyed the following to
comp.os.linux.setup...

Probably dropped back into the feed by a broken BBS. Happens quite a
lot, and this is how alt.os.linux.gentoo got spammed to death -
literally, because all of its occupants have moved over to mailing lists
on gmane.org.

--
= Aragorn =

http://www.linuxcounter.net - registrant #223157

[Bobbie Sellers]

I assumed that being a gmail user the poster had been digging in the
archives there. Maybe i see trolls and spammers that are not there.

bliss

[Aragorn]

On Wednesday 09 July 2014 06:39, Bobbie Sellers conveyed the following

Ah yes, Google Gropes. :p That explains why I have not seen the
original reply. I filter out Google Groups posters for most of the
newsgroups I'm in - there are exceptions, but they are rapidly shrinking
in number :p - and the above is only one of the many reasons why. ;-)

[Michael Black]

No, it's google.

From the headers:
Complaints-To: groups...@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;

Michael

[John Hasler]

Aragorn writes:
> Probably dropped back into the feed by a broken BBS.

Michael Black writes:
> No, it's google.

Yes. A broken BBS.
--
John Hasler
jha...@newsguy.com
Dancing Horse Hill
Elmwood, WI USA

[Aragorn]

On Wednesday 09 July 2014 17:41, John Hasler conveyed the following to
comp.os.linux.setup...

> Aragorn writes:
>
>> Probably dropped back into the feed by a broken BBS.
>
> Michael Black writes:
>
>> No, it's google.
>
> Yes. A broken BBS.

So broken that the first "B" has fallen off, and now only the "BS"
remains. :p

[The Natural Philosopher]

On 09/07/14 18:17, Aragorn wrote:
> On Wednesday 09 July 2014 17:41, John Hasler conveyed the following to
> comp.os.linux.setup...
>
>> Aragorn writes:
>>
>>> Probably dropped back into the feed by a broken BBS.
>>
>> Michael Black writes:
>>
>>> No, it's google.
>>
>> Yes. A broken BBS.
>
> So broken that the first "B" has fallen off, and now only the "BS"
> remains. :p
>

:-)

[Michael Black]

On Wed, 9 Jul 2014, John Hasler wrote:

> Aragorn writes:
>> Probably dropped back into the feed by a broken BBS.
>
> Michael Black writes:
>> No, it's google.
>
> Yes. A broken BBS.

No, it's google and they still have the bug that allows replies to
messages older than 30 days.

I have no idea why someone replied to an old message but didn't bother to
add anything, but this wsa deliberate. I've seen it plenty of times,
speculation in other groups is that someone is "testing", before they use
an old message to spam the newsgroup. I've certainly seenthat, a post
with only quoted text, then the next the same old quoted message with some
text.

I remember the days when it wasn't uncommon to come across old messages
that had been retransferred because someone had msiconfigured or had some
other gitch at a newsserver. But that hasn't happened in quite some
years, likely a result of "nobody likes usenet" so no amateur is playing
with the software. The fewer sites for usenet, the less likely there will
be glitching.

Michael