> Seems I spend more time fixing my Wife's computer
> that anything else.
> Her mother board went out and I bought a new mother
> board but Windows XP will
> no longer boot. It comes up in the BIOS and setup
> fine. Naturally she did
> back up here data and I would like to get that drive
> to boot.
>
> Paul Lamar ...No rotor no motor.
Drivers are different!!!
Just reinstall Windows on the same drive and use
c:\Winnt for the windows folder and do not format the
drive. All the data will be on the drive in the same
folders as before.
Bryan
She lost the disk years ago and they want $200 for a new OS.
New computers don't come with OS disk. If your computer
breaks you are SOL.
Why don't they put all the drivers on the hard disk anyway during
the first
install? The computer is a computer. It should be able to
figure out
what drivers are needed and load them off the hard disk and install
them. An IDE is an IDE. Linux has no problem.
What is a couple of hundred K for drivers when the OS is over a
gig?
We fixed DOS computers for fifteen years without all this hassle.
My wife drives me crazy with this stupid thing. Linux is 1/100 of
the trouble.
If I need a new OS I go to the book store and buy a new one
along with
a magazine for $9.95.
BTW Fry's has a new mother board about 6.5 by 6.5 inches WITH 1
gigi
hertz
CPU for $169. Perfect for a glass cockpit. It is called an
EPIA-1000.
You can get a Syba Compact flash to IDE host interface card for
$12.95.
A four gig solid state compact flash drive will then store the
program and
data with no hard drive required.
Could be used with DOS as a engine monitoring display driver
and data acquisition system. I have some moving map software
that runs
on DOS taking in data from a GPS every 2 seconds. It also records
your lat long
position, altitude, speed and heading once two seconds as well. 10
meg will
store hours of flight. Complete with the FAA runway data base.
Also the PICAXE can talk to DOS in real times so DOS is not a
bad way to
go. You could use this computer to control the fuel injection
as QB is
a real time basic. On a gigi hertz processor compiled QB would
be very powerful as a fuel injection system. Hardware
technology marches
on and software is going backwards.
Paul Lamar ...No rotor no motor.
Ughh, DOS. Just kidding (sort of)..
Anybody here work with a Real-time OS? I have always been kind of
curious about how a real time version of Linux differs from a regular
one. Just stripped out? I'd think a real-time OS would be good for
something like engine management and monitoring..
http://en.wikipedia.org/wiki/Real-time_operating_system
<http://en.wikipedia.org/wiki/Real-time_operating_system>
http://www.realtimelinuxfoundation.org/
<http://www.realtimelinuxfoundation.org/>
Matt-
Me. I wrote my own real time OS back in 1976 on a 6502 in assembly
language.
My road test system would take in data every few milliseconds
process it,
display on the instrument panel with an LCD, and send it to the
printer in
real time while the printer is printing. All using a ONE megahertz
processor
and 2K of EPROM and ONE K of RAM! I also designed and manufactured
the SuperKIM
mother board. Probably the first commercial application of an
embedded microprocessor.
For sure the first real time multitasking microprocessor software.
Before the Apple II.
Read all about it:
Microprocessor-Based System for Roll-Down and Acceleration Tests
by D.K. Lynn, C.R. Derouin, and Paul Lamar
Los Alamos Scientific Laboratory
Published in IEEE Proceedings 29th Vehicular Technology Conference
(The technical details of the Lamar Instruments real time road test
system.
The Phd's get to have their name before mine :))
Arlington, Illinois, March 28-30, 1979
http://www.computer-dictionary-online.org/?q=6502
http://www.hansotten.com/indexkim.html
<http://www.hansotten.com/indexkim.html>
http://www.kim-1.com/docs.html
Well When Windows came out they busted a lot of real time
applications because
you could directly access the hardware using QB running on DOS.
There were instructions called IN and OUT that directly accessed the
hardware at light speed. PEEK and POKE did the same thing.
All that is gone.
Paul Lamar ...No rotor no motor.
Cool.. You've got me beat on, "How slow was your processor?" But we're
marched on, "How small was your program?" We did autonomous
"firefighting" robots with Mot HC11's with 8MHz processor and 1K of
RAM. Started with assembly programs, but ended up writing the
deliverable code in C. What a hoot.
Back in the day, we were monkeying around with trying to mimic PEEK/POKE
(inport/outport, actually) on a linux box, but with the distribution we
were running, we had to add some kernel modules and then we had weird
stability problems that we never figured out. I suspect all of that
kind of thing has been solved (and documented nicely) now, but haven't
been back to look.
Matt-
The Rotary Engine NewsLetter. Powered by Linux.
ACRE NL web site.
http://www.rotaryeng.net
Copyright 1998-2006 All world wide rights reserved.