TIP: Click on subject to list as thread! ANSI
echo: linux
to: ALL
from: WAYNE_CHIRNSIDE@f140.n123.z1
date: 2005-10-26 21:08:20
subject: software for linspire

Path: number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.adelphia.com!news.adelphia.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 26 Oct 2005 21:08:20 -0500
Newsgroups: fidonet.linux
From: WAYNE_CHIRNSIDE@f140.n123.z1
Date: Sat, 22 Oct 2005 03:23:58 -0400
Subject: software for linspire
Message-ID: 
Organization: Try Our Web Based QWK: DOCSPLACE.ORG
 456
 205/1
 267/200
Lines: 31
NNTP-Posting-Host: 24.48.121.215
 properly
Xref: number1.nntp.dca.giganews.com fidonet.linux:30

-> CA>>>>>> Although I can agree that past implementations have
-> CA>>>>>> been iffy at best I continue to believe that all PC
-> CA>>>>>> BIOS should be loaded as file(s) from rewriteable
-> CA>>>>>> storage media. 

-> WC>>> I still like flashable NVRAM. 

-> ->> Flash one with the wrong software and then you won't like
-> ->> NVRAM as much. ;-) 

-> WC> I've flashed one so far without difficulty, older machine
-> WC> too. 

-> Like I said, flash one with the wrong software and you'll not
-> like NVRAM so very much anymore. 

-> WC> I researched and looked into documentation a LOT before
-> WC> proceeding. 

-> WC> I understand the risks and some of the motherboard
-> WC> manufacturers are now offering dual NVRAM so you can boot
-> WC> your system and clean up the badly flashed NVRAM. 

-> Putting only a bootstrap loader into ROM and the BIOS as a file
-> or files on rewriteable media would eliminate the risks
-> involved in updating the BIOS. 

ROM would work but if socketed subject to poor connections failures and
corrosion of contects.

We're just going to have to agree to disagree on NVRAM. 

SOURCE: echoes via archive.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.