Can I make an RC5 boot disk?

[Sukhoi]

Would it be possible to make a bootable floppy, put the DOS RC5 client on the floppy, and stick a command in the autoexec.bat file to automatically start it crunching? I realize I would manually have to fetch and flush with my home client. But this way I could keep the disk with me and then whenever I'm at a place where the computers aren't being used, I could stick the disk in, reboot the computer, and get a little processing time without actually having to load something on the computer.

Oh, I just thought of another question. Will WinNT 4.0 boot off of a floppy normally? Or can the OS be setup to bypass the floppy on bootup? I know the BIOS can be set to boot C: first, but I'm just worried about the OS for now.

 

[DanC]

You are describing Klinux actually....

It's the most efficient floppy client known to man or beast.

But, it should be possible with DOS - given enough space on the disk.

edit (again) yes - NT can be booted from floppy if the machine is set to look at the floppy drive.

 

[Train]

I ran a boot disk RC5 from DOS, the keyrate blows, go with Klinux

 

[JHutch]

I agree with Train. The DOS method works, but the DOS client sucks large monkey balls... Go with KLinux. It'll do exactly what you're looking for and faster, too!

JHutch

 

[DanC]

As a "fer-instance"...

I have two lower-end machines.

The K6-2/350 did 512 Mkeys/s on Win95.
The PPRO 180 does 517 running Klinux.

Klinux is the ticket.



<< &quot;Large Monkey Balls&quot; >>

- dasm... you're cracking me up.

 

[divide by zero]

Of course, you can't store the buff-in &amp; buff-out on the Klinux disk. You have to have internet access to fetch and flush or access to a local personal proxy (pproxy) that has been loaded with blocks - either manually or via the internet.

[Edit]
So, for a buff-in &amp; buff-out you carry in your pocket, DOS is the way to go as far as I can tell.
[/Edit]

 

[Bartman]

where can I get it and is there a boot dist that can load nic drivers for a 3com card.. or some ne2000 driver, then connect to a dhcp server for an ip?

is there a seti boot disk that could do this too?

Bart

 

[Kilowatt]

L@@K


:|
:|
:|:|:|
:|:|:|
:|

 

[Sukhoi]

It should be possible with SETI, but I don't know of anyone that has actually made a Linux boot disk for it yet.



<< So, for a buff-in &amp; buff-out you carry in your pocket, DOS is the way to go as far as I can tell. >>



Yeah, I didn't think Klinux would store the buff in &amp; out files on the floppy. I guess some cracking is better than none though.

 

[Dantoo]

There's got to be a way to do this already.

Use the Klinux boot disk to get up and going.
Carry a diskette with a buff-in and buff-out file on it (nothing else needed)
Point the client during configuration setup at the remote buffer (floppy).
Sneakernet buffer disk to Internet machine as appropriate

It looks to me as if the tools are already in the client, I just can't see my way through it yet.
I'm thinking that something along the line of defining the &quot;buffer file-name prefix&quot; into a linux/floppy path might do it, but I'm not sure. As I understand Linux (and I don't) the devices are all wrapped seamlessly into the file system so it should be easy??
Surely somebody here has done it this way already.

 

[Kilowatt]

<< I didn't think Klinux would store the buff in &amp; out files on the floppy. >>

I have tried it on a test version I did, and it worked.
I thought that would be a cool addition to the next Klinux release, but then I thought people would start getting dupes, by using the same floppy over again in a different node.

I'm tiring to make Klinux &quot;Newbie Proof&quot; and scraped the script.

I've talk to a few freinds who use Klinux, and being able to save your dnetc.ini file to another floppy was really all that's needed.
If you set your buffers low enough (32 WUs), you won't be wasting much.
If Klinux were to crash on ya, you already lost everything.

 

[Kilowatt]

Hmmmmm.......

You guy asking for a version that doesn't use networking?
Just boot the kernel, fire up the client and import/export some WU buffers?

A Klinux sneakernet version?
It sure would decrease the size of the kernel without nic drivers, I could then add Dos support.

Hmmmm............

 

[Viztech]

Klinux 'S' Series.....

Available soon at a server near you!

viz

 

[Fardringle]

Kilowatt,

Whether or not it would influence you in making a version like that, I must say that I too would be VERY interested in a Klinux version that I could just pop into a few of the machines here at work that don't have internet access!!

 

[Kilowatt]

<< Whether or not it would influence you in making a version like that... >>

It wouldn't be that big a deal, just the kernel is all that would be different.

I'd leave the basic dnet client in it.......scratch that.
If I left out the client, and enabled Dos support, the OGR people could install the 462 version of the Linux client, and get better &quot;Rulers&quot; or what ever it is they get.

It may even let the Seti people install their stuff, to help them look for little green men. ;p
But I think they'll need plenty of memory in the Rack boards.
8MB won't cut it I don't think.

This won't happen overnight, or even next week.
I'll be moving into a bigger storefront the first of the year, and it'll probably take me a while to get all setup and settled.

I need to see if just the Klinux.img will download, without being zipped.
It sure would be easier on me to get newer versions out.

OH Well, I'll think about it.