Help please!

I have a shuttle-X.  It has no fdd.  it has no cd.  It has USB and no O/S.  It 
has a network port.

It does do "post" and it runs the BIOS fine.  It sees the KB and the monitor 
and it can support six (6) of them.  It has apparently an athalon 2300+ CPU 
that runs hotter than a * on pay day.  

I have been on the phone with Shuttle Tech support and they say this puppy can 
boot off a USB stick.  I'm not sure I believe them.  The puter is a model SN41G.



I have tried to create a bootable USB stick from an ubuntu 10.10 .iso


This should be easy.

format the USB stick

Copy the OS files in.

note the location (sector number) of the stage #2 loader.

Put this address into the mbr

use dd to write the new mbr to sector zero.

the dd cammand to do this providing I have the sector created is

dd if=blah of=/dev/rsdoc count=1

That is on the OpenBSD pupppy


I tried 

dd if=kubuntu--10.10-desktop-i386.iso of=/dev/rsd0c bf=32k

This is copy the whole .iso into the USB stick.  It worked.  I can mount it.  
its iso9660 format.  Maybe it needs msdos vfat format.  I don't know.

The BIOS doesn't know.  it reads sector zero.  Why do I need to know something 
about goats

What am I not understanding?

I made the stick on my OpenBSD machine.

It has working USB and my debian sarge machine is borken.  I can likely get usb 
running on this old puppy but I need to rebuild module usb-uhci.o   I can do 
this.

My objective is to get the new puppy running and copy everything in the old 
puppy to archives and migrate to new w/o tampering with borken puters.


Next I want to get the six (6) head puppy running with virtual box and load mac 
LION in and there is a snow leopard here... 

When I get this new puppy running I'm calling it Dog.

Like in Dog Team.  With six (6) heads.  Dog will be at our next install fest!




_______________________________________________
clug-talk mailing list
clug-talk@clug.ca
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to