> I'm in Perth, Western Australia and would be happy to loan them to someone
> in this region if that helps.
The offer is appreciated :)
I am in Atlanta, Georgia, USA (on the east side in a crummy little
town called Clarkston, right next to the railroad tracks)...not exactly
walking distance from Perth. Perhaps there is another ELKS developer in
Perth who would be interested? Or perhaps someone with a flatbed scanner
and a lot of time on their hands?
Right now I am simply copying the necessary .c and .h files for MCA and
ESDI support from the linux 2.2.14 source directly into the elks source
directory. We shall see what happens at compile time. I've created a
directory called "drivers" and in that, a directory called "block" for
block device drivers such as ps2esdi.c, coming straight out of the linux
2.2.14 source.
Is there a way to run bcc on a file or set of files to see where the
problems will lie with regards to moving from 32-bit instructions to
16-bit instructions? Having only been learning C for 3 weeks now, I'm
still not quite able to pick out problems with changes in system
architecture :)
-matt balaun
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Shadow Daemon, aka mAtT bAlAuN
I love to eat them smurfies,
Smurfies what I love to eat.
Bite they ugly heads off,
Nibble on they bluish feet.
