Is the TCP/IP project totally dead, or is someone still working on it? I
have an ATT PC6300 just waiting for me to install ELKS on it, but
without a TCP/IP stack, it is of limited use to me. I **really** want to
put it back into service!! Thanks - Larry
AFAIK nobody's doing anything. I saw
Hallo ELKS-friends !
I have a problem with my 3COM 3C509B ISA/PnP card.
I can use 16KB boot roms, but if I want to use 32KB
eproms (like 27C256B), the config tool 3c5x9cfg.exe
set a range of for example c8000-cbfff, but 32KB
should be c8000-c. Only the first 16KB can be used.
Why, where is
Hello,
Does anyone have an idea of witch EPROM's are compatible with the 3com
509bCombo NIC for use in the boot prom slot ???
Cheers
G
It will take 8kB, 16kB or 32kB (2764, 27128, 27256). Usually you will
see a C after 27, that means CMOS == lower current consumption.
Take a a.out executable and convert it to a hex dump of the memory it will
occupy (once loaded) and then transfer it across to the machine, and jump to
the base location.
How can I do the expanding bit? Are the tools out there already? Or do I
have to code it myself?
GNU objcopy might do the
IMHO, and if my rusty RAM serves, an 8253 was the normal serial chip on the
old CP/M and early DOS machines.
Er no, the 8253 is a programmable interval timer made by Intel. You may
be thinking of the 8250, a UART made by National Semiconductor.
How do Video BIOS make sure they are executed before everything else?
Video BIOSes are looked for as a special case. They are normally located
from C to C8000.
I am now stuck. I have tried a 3c509B, an SMC Ultra, and SMC 'Western
Digital' card, and various older NICS, and none of them take more than 32K.
The only remaining options are purpose build cards.
Another possibility is two NICs with a 32kB ROM each.
I have a 3c905 in my desktop machine which can take 64K or 128K, but it is
not clearly documented anywhere I can find which end of the socket I am
supposed to put the ROM, and I could not get it to work in either end when
I tried it in both. The other problem is that this card is PCI, so wont go
I am now stuck. I have tried a 3c509B, an SMC Ultra, and SMC 'Western
Digital' card, and various older NICS, and none of them take more than 32K.
The only remaining options are purpose build cards.
Have you considered using a compressed ROM image like Etherboot does? With
that you could get
The code Christian has contributed does just this, though I have not yet
been able to get it to work as I am still tracking down a network card that
will take a 64K ROM. I have the plans for a flashcard, but have not yet
been able to get thte parts to build one.
I've seen some NE2000 clones that
Sorry, my fingers wasn't syncronized with my brain. What I meant was:
So we are back to the usual problem, where in the 640kB..1024kB range should
we
put or own EPROM.
Somewhere free from C8000 to F.
Actually, 'format' simply means 0x55aa at the start of the image, and the
3rd byte contains the number of 256 byte pages in the ROM. Nothing else
is involved in the 'format'.
0x55aa
number of 256 word = 512 byte pages
entry point, entered with long jump and cs = segment of ROM
All the bytes in
I have come across a few old machies that had sockets like this, but never
one that actually had a BASIC rom in it. I don't know what the ROM in this
socket needs to contain in order for the BIOS to recognise it as a BASIC
ROM and run it if boot fails.
I think the BASIC ROM has a particular
http://www.zilog.com/ez80/
Someone now design a cool linux box with the ez80.
Would it be possible as it has a MMU and supports 16mb of memory ?
I looked at the datasheets and there are a couple of things that would
make life harder for compiler writers. In Address Data Long mode (what
they
Seen on /. Zilog announces the eZ80.
http://www.zilog.com/ez80/
Mentions a TCP/IP stack too.
As far as I was told, the Zilog company was founded by some developers from I
ntel that disagreed on the calling convention(and probably other things too)
Not quite, Zilog wanted to build a superset of the 8080. Also it had
simpler hardware interfacing, single 5V supply instead of several,
I thought the Z80s were near 8088s or 188s...am I on Dr Pepper again???
No, they are more like 8080s. 8088s are 16 bit machines, whereas the
Z80 remains an 8 bit machine.
Personally I think if as86 code were converted this way, you keep the
as86 users happy.
There's another advantage with this means of conversion that I forgot
to mention. By using macros to retain compatibility with as86, it's
easy to do regression tests to ensure the semantics of the code have
I'm translatting the assembler source code of Linux (as86) to Nasm
syntax. I need to understand the syntax of as86 wich is (very??)
different from Nasm's one, in particular :
Ye gods. Umm no idea
movb4(di),*36; (What mean the * prefix of value 36)
Yes, BCC doesn't even check prototypes when the "-ansi" switch is
given. It just pipes the text through unprotoize.
Sorry, please explain to me again what we would gain by using the P()
macros that unprotoize doesn't already do? I mean, isn't the source
already or potentially ANSI syntax
I bet it definitely works (boot on XT drive) if one disables the onboard
IDE first.
The problem I see is using IDE and MFM/RLL drives at the same time,
which might prove difficult.
To boot XT drives on an AT+, one usually has to disable the IDE drives
so that the BIOS doesn't go looking there.
The story I got told was there was something amiss with the Stacks on
the MOS 6502, like they're not big enough or something. Anyone hear
about this?
On the 6502, the high byte of the stack pointer is the constant 01 so
the stack has to live on page 1; 256 bytes worth.
Can anyone tell me if the "t" mode for executables does anything.
Sometimes referred to as the "sticky bit", it is supposed to make an
executable stay in swap space after it is run, so the next time it
is run it simply swaps in and executes.
Not anymore in modern Unixes.
BTW, linux-8086 is not
That uses (3) as a "transparent print spooler", as per my quoted
comment, and the development of a "translating print spooler" using
utilities such as ghostscript (can that be easily ported to ELKS)
would follow from there.
Transparent print spoolers will work but I think translating print
I have an 8086 that I'd like to use for some embedded projects. One of
these is the dream of many linux people: the toaster that runs linux.
Hehe... 'telnet toaster'... Anyways, I have a bunch of EPROMs that I'd
like to program, but I can't get the silly things to erase. They're
supposed to be
I'm new to this list and am wondering if the message below means to
imply that an 8086 system with expanded memory is not supported
because drivers for all the different bank-switching schemes do not
exist. I have the same question for 80286 systems with extended
memory cards.
Expanded memory
http://www.bgnett.no/%7egiva/
Gisle Vanem did this work. It includes a BSD socket style API. It might
be of some use to ELKS.
: * Usage: /bin/date
: * date [?[?]] | date
One small point: Isn't '?' a shell wildcard character? This means that if w
ildcards
are enabled on the shell (currently not with ELKS, but should be) then the
? will have to be escaped? Perhaps we should use a more standard option
scheme,
This appeared in slashdot.org, maybe it's much easier to deal with than
the x86 architecture.
http://www.rpcgllc.com/rpcgproducts.htm
Anyway it's getting a bit off-topic for this list.
29 matches
Mail list logo
