Menu
▾
▴
linux-apus-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
| 2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
| 2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
| 2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: <fp...@zu...> - 2000-08-02 07:01:49
|
I have tried to write kernel images to an AFFS partition. If I diff source and target after writing, I get differences, always. Not so in 2.2.10. The AFFS partition is ~2G, maybe that is a problem? -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
|
From: <fh...@at...> - 2000-08-02 02:31:25
|
I'm going to try the 53c770 driver as memory mapped, when I compile it that way and try to insert the module I get undefined symbols readw_l2b, writew_b2l, writel_b2l, and readl_l2b. Does anyone know what these are? I've assumed that b2l means "big to little" etc. I'm not totally sure I should get those errors though because I believe the Power PC and 53c770 are both big endian. Fred |
|
From: <fh...@at...> - 2000-08-02 02:20:08
|
I've added my two Zorro cards to /usr/src/linux/include/zorro.h For example I added ZORRO_PROD_VMC_HYPERCOM_4_PLUS \ ZORRO_ID(VMC, 0x06, 0). However, when I compile the kernel with the new definition and try to use zorro_find the card is not detected. i.e. key = zorro_find( ZORRO_PROD_VMC_HYPERCOM_4_PLUS, 0, 0); The board does not get "found". What have I missed? Fred |
|
From: <fh...@at...> - 2000-08-02 01:53:41
|
In <Pin...@en...>, on 08/02/00 at 08:08 AM, No Spam <no...@no...> said: >On Tue, 1 Aug 2000, Gordon Huby wrote: >> signal.c >> signal.c: In function `do_sigaction': >> signal.c:921: fixed or forbidden register 68 (0) was spilled for class CR0_REGS. >> This may be due to a compiler bug or to impossible asm statements or clauses. One problem I've noticed with the built it myself compiler (I don't know if the problem I will describe comes from there though) is that the temporary assembler files sometime seem to not get written fully or are corrupted by the compiler before the assembler attempts to assemble them. At least that's the only explanation I can come up with. I get an error something like invalid assembler instruction or parse error. Restarting the compile *most* of the time seems to eliminate the error, but not all the time. Fred |
|
From: Ken T. <ke...@we...> - 2000-08-02 00:58:32
|
On Wed, 2 Aug 2000, Glenn Hisdal wrote: > I got that too. > Updating to the latest gcc compiler fixed the problem. What version and where from ? > I still can't get the cybervision64 driver to work in 2.4 though (It > compiles fine, but I can't use it). > The kernel just uses amifb:vga even if i tell it to use cyberfb... I suspect many things in video/graphics department in 2.4. Ken. |
|
From: Glenn H. <gh...@c2...> - 2000-08-01 22:24:13
|
Hello, > On Tue, 1 Aug 2000, Gordon Huby wrote: >> signal.c >> signal.c: In function `do_sigaction': signal.c:921: fixed or forbidden >> register 68 (0) was spilled for class CR0_REGS. This may be due to a >> compiler bug or to impossible asm statements or clauses. > Same error I get. > Ken. I got that too. Updating to the latest gcc compiler fixed the problem. I still can't get the cybervision64 driver to work in 2.4 though (It compiles fine, but I can't use it). The kernel just uses amifb:vga even if i tell it to use cyberfb... - glenn |
|
From: Ken T. <ke...@we...> - 2000-08-01 22:15:23
|
On Tue, 1 Aug 2000, Michel [iso-8859-1] Dänzer wrote: > Ah, Ken had the same problem, also using egcs 1.1.2 . I could build it using > gcc 2.95.2 . And the kernel even booted! :) Is your gcc a 'build it at home in an evening' or from a distribution ? Ken. |
|
From: No S. <no...@no...> - 2000-08-01 22:13:58
|
On Tue, 1 Aug 2000, Gordon Huby wrote: > signal.c > signal.c: In function `do_sigaction': > signal.c:921: fixed or forbidden register 68 (0) was spilled for class CR0_REGS. > This may be due to a compiler bug or to impossible asm statements or clauses. Same error I get. Ken. |
|
From: Michel <dae...@st...> - 2000-08-01 21:43:39
|
Gordon Huby wrote: > signal.c: In function `do_sigaction': > signal.c:921: fixed or forbidden register 68 (0) was spilled for class > CR0_REGS. > This may be due to a compiler bug or to impossible asm > statements or clauses. Ah, Ken had the same problem, also using egcs 1.1.2 . I could build it using gcc 2.95.2 . And the kernel even booted! :) Michel -- Secret hacker rule #11: hackers read manuals. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Gordon H. <go...@gh...> - 2000-08-01 21:36:18
|
Michel Dänzer wrote: > > I would like to compile 2.4, but It refuses to compile with egcs 1.1.2. > > Should I switch to gcc? > > I recommend upgrading to the latest gcc (I have 2.95.2), however not all > compiling problems are due to the compiler. Please post the problems you have. |
|
From: Michel <dae...@st...> - 2000-08-01 16:56:16
|
Rudi Chiarito wrote: > > On Sun, Jul 30, 2000 at 09:04:31PM +0200, Geert Uytterhoeven wrote: > > > I've been looking at APUS' support for Zorro Ethernet cards and it > > > doesn't seem that encouraging. The FAQ, which is quite old, lists only > > > the A2065, the AriadneI/II and the Hydra as supported. > > And PCMCIA NE2000 clones through the apne driver? > > That's another thing that puzzled me. Chapter 6 of the FAQ, located at > <ftp://linux-apus.sourceforge.net/pub/linux-apus/docs/working.html>, > makes no mention of any PCMCIA hardware. There's a mention though at > <ftp://linux-apus.sourceforge.net/pub/linux-apus/docs/getting-the-kernel.html#INCLUDED-HARDWARE-DRIVERS> The FAQ hasn't been updated or maintained for a very long time... Michel -- Life is a journey. Are we there yet? Are we there yet? Are we there yet? ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Michel <dae...@st...> - 2000-08-01 16:37:43
|
Gordon Huby wrote: > > > > I'd like to have mainly only bug fixes (apart from the upgrade to > > > > 2.2.16, if anyone really wants to do that...) in the 2.2 tree from now > > > > on. > > > > > > 2.2.16 supports IP Masquerading, So I would like to see that done. > > > > 2.4 also supports that, it even provides compatibility to 2.2 ipchains. > > Thats good to hear. > > I would like to compile 2.4, but It refuses to compile with egcs 1.1.2. > Should I switch to gcc? I recommend upgrading to the latest gcc (I have 2.95.2), however not all compiling problems are due to the compiler. Please post the problems you have. Michel -- Be vewy vewy quiet! I'm weloading! ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Alan B. <al...@ms...> - 2000-08-01 09:58:03
|
hi, > > I was interested in getting an X-Surf, but apparently there's no driver > > What is X-Surf ? What speed is it, 10, 100 (gigabit ;) ? its a Zorro card that has an ISA ethernet card as part of its design. it also has clockports and IO ports . Its been out for about 4 months now (or so...) so I'd expect a lot mroe requests regarding this hardware to appear. alan |
|
From: Rudi C. <ru...@am...> - 2000-07-31 23:49:14
|
On Sun, Jul 30, 2000 at 09:04:31PM +0200, Geert Uytterhoeven wrote: > > I've been looking at APUS' support for Zorro Ethernet cards and it > > doesn't seem that encouraging. The FAQ, which is quite old, lists only > > the A2065, the AriadneI/II and the Hydra as supported. > And PCMCIA NE2000 clones through the apne driver? That's another thing that puzzled me. Chapter 6 of the FAQ, located at <ftp://linux-apus.sourceforge.net/pub/linux-apus/docs/working.html>, makes no mention of any PCMCIA hardware. There's a mention though at <ftp://linux-apus.sourceforge.net/pub/linux-apus/docs/getting-the-kernel.html#INCLUDED-HARDWARE-DRIVERS> > Which Realtek chip? I guess the RTL8019AS? That would be the most logical > choice. http://www.jschoenfeld.com/products/xsurf_e.htm only mentions "Realtek chipset". Though it also says "all programming docs open (for Linux-drivers)". > Is the full programming documentation available in electronic form? If you > send it to me, I might even adapt ariadne2.c myself... I'll inquiry individual Computers. > > The AriadneII could be the second option, but the FAQ says it runs at 10% > > the speed of the Amiga (SANA) driver. Have things improved in the > > meantime? The cards also seem to be harder to find, BTW. > That's weird. AFAIK the Ariadne II driver gets nearly 1 MB/s if you have a > fast CPU. Since that's close to the theoretical limit of Ethernet, I don't > think there's much area for improvement. I was just reporting what the FAQ says. Maybe the above is based on an older version of the driver? > > Any suggestions? > Buy an X-surf, and get it to work :-) I'll try that. The problem is that I've already had to mess too much with Linux sources lately, hacking others' stuff (RedHat's) while I'm supposed to do something else. ;) The bug-fixing procedure was so cumbersome and painful that I don't feel like getting into anything similar anytime soon. Hopefully, with the helpful explanations you made, it won't take much effort. ;) -- "A true zen saying, nothing is what I want" (Frank Zappa) Rudi Chiarito SGML/XML, user interface, i18n Amiga Inc. ru...@am... http://amiga.com/ |
|
From: Gordon H. <go...@gh...> - 2000-07-31 20:54:46
|
Michel D?nzer wrote: > > Yes, but unregister_serial and register_serial are in apus_setup.c. > > > > So why don't the modules see that symbol? > > I imagine because there is no EXPORT_SYMBOL for them - they could be added to > arch/ppc/kernel/ppc_ksyms.c I guess. Yes, that would explain it. :) > > > I'd like to have mainly only bug fixes (apart from the upgrade to 2.2.16, if > > > anyone really wants to do that...) in the 2.2 tree from now on. > > > > 2.2.16 supports IP Masquerading, So I would like to see that done. > > 2.4 also supports that, it even provides compatibility to 2.2 ipchains. Thats good to hear. I would like to compile 2.4, but It refuses to compile with egcs 1.1.2. Should I switch to gcc? Kind Regards, Gordon. |
|
From: Geert U. <ge...@li...> - 2000-07-31 16:21:16
|
On Mon, 31 Jul 2000, Ken Tyler wrote:
> On Sun, 30 Jul 2000, Rudi Chiarito wrote:
> > I was interested in getting an X-Surf, but apparently there's no driver
>
> What is X-Surf ? What speed is it, 10, 100 (gigabit ;) ?
AFAIK all Amiga Ethernet cards are 10 Mbps only. These days the RTL8019AS
(an ISA chip) seems to be the best choice since it's very cheap and doesn't
require much glue to connect to the Zorro bus.
Faster Ethernet chips are usually PCI and require PCI busmastering to work,
which is a bit more complex than the simple Zorro-PCI FPGA bridges used in
graphics cards with PCI graphics chips. But it can be done: the DKB Wildfire
accelerator must have a better PCI bus since it seems to have a DEC21041
on-board (from looking at pictures, never saw one IRL, nor do I know anyone who
owns one).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: <fh...@at...> - 2000-07-31 12:24:37
|
In <398...@ip...>, on 07/30/00 at 09:51 PM, Giorgio Terzi <de...@ip...> said: >fh...@at... wrote: >I can only answer for serial driver's code: >With IOBlix driver i found a similar problem with register_serial() & >unregister_serial() functions. >I used m68k_register_serial() & m68k_unregister_serial() instead, >interfacing myself with Roman Hodek's m68kserial driver and the problem >was solved. Changing to the "m68k" functions and adding -O to the gcc options fixed all the undefined symbols problems. Thanks! Fred |
|
From: Geert U. <ge...@li...> - 2000-07-31 11:24:13
|
On Sun, 30 Jul 2000, Rudi Chiarito wrote:
> I've been looking at APUS' support for Zorro Ethernet cards and it
> doesn't seem that encouraging. The FAQ, which is quite old, lists only
> the A2065, the AriadneI/II and the Hydra as supported.
And PCMCIA NE2000 clones through the apne driver?
The Hydra driver is probably no longer functional, since it's been a while ago
that it actually compiled, IIRC.
> I was interested in getting an X-Surf, but apparently there's no driver
> for it. I know that it comes with full programming documentation and that
> it shouldn't be impossible to adapt an existing driver for Realtek
> chipsets, but these days time definitely isn't something I have plenty
> of. ;(((
Which Realtek chip? I guess the RTL8019AS? That would be the most logical
choice.
If that's the case, you probably have to change only a few of the first 16
#define's in ariadne2.c and replace ZORRO_PROD_VILLAGE_TRONIC_ARIADNE2 by the
Zorro ID of the X-Surf (0x12121700, if I'm not mistaken). All the rest in the
driver is plain NE2000 stuff.
Is the full programming documentation available in electronic form? If you
send it to me, I might even adapt ariadne2.c myself...
> The AriadneII could be the second option, but the FAQ says it runs at 10%
> the speed of the Amiga (SANA) driver. Have things improved in the
> meantime? The cards also seem to be harder to find, BTW.
That's weird. AFAIK the Ariadne II driver gets nearly 1 MB/s if you have a
fast CPU. Since that's close to the theoretical limit of Ethernet, I don't
think there's much area for improvement.
> Any suggestions?
Buy an X-surf, and get it to work :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Ken T. <ke...@we...> - 2000-07-30 21:47:11
|
On Sun, 30 Jul 2000, Rudi Chiarito wrote: > I was interested in getting an X-Surf, but apparently there's no driver What is X-Surf ? What speed is it, 10, 100 (gigabit ;) ? > for it. I know that it comes with full programming documentation and that > it shouldn't be impossible to adapt an existing driver for Realtek > chipsets, but these days time definitely isn't something I have plenty > of. ;((( Ken. |
|
From: Michel <dae...@st...> - 2000-07-30 20:05:27
|
Gordon Huby wrote: > > > > ser_hypercom4.o: unresolved symbol unregister_serial > > > > ser_hypercom4.o: unresolved symbol register_serial > > > > > > > > Fred > > > > > > > > > > I can only answer for serial driver's code: > > > With IOBlix driver i found a similar problem with register_serial() > > > & unregister_serial() functions. > > > I used m68k_register_serial() & m68k_unregister_serial() instead, > > > interfacing myself with Roman Hodek's m68kserial driver and the problem > > > was solved. > > Yes, but unregister_serial and register_serial are in apus_setup.c. > > So why don't the modules see that symbol? I imagine because there is no EXPORT_SYMBOL for them - they could be added to arch/ppc/kernel/ppc_ksyms.c I guess. > > This may be a quick fix for that problem, however AFAIK the m68kserial isn't > > accepted by Linus and isn't in the native tree nor our 2.4 tree, which should > > really be our primary development target now. There's a new amiga serial > > driver - amiserial.c - in 2.4 . > > I think I did mention that to Fred :-) Anyway I'm working on a new > driver for 2.3. This time, the hypercom1 driver is going to use the > generic_serial.c code. Very good! > > I'd like to have mainly only bug fixes (apart from the upgrade to 2.2.16, if > > anyone really wants to do that...) in the 2.2 tree from now on. > > 2.2.16 supports IP Masquerading, So I would like to see that done. 2.4 also supports that, it even provides compatibility to 2.2 ipchains. Michel -- [I'm in MacOS here, so no funny .sig ;] |
|
From: Gordon H. <go...@gh...> - 2000-07-30 19:45:17
|
Michel Dänzer wrote: > > Giorgio Terzi wrote: > > > > fh...@at... wrote: > > > > > I decided to try developing my driver projects as modules in order to save > > > reboot cycles. When I do this, trying to follow the module programming > > > advice I got, I get unresolved symbols. How do I get rid of these? These > > > symbols appear to be routines burried in the kernel various places. > > > > > > The Hypercom4+ module: > > > > > > ser_hypercom4.o: unresolved symbol queue_task > > > ser_hypercom4.o: unresolved symbol mark_bh > > > ser_hypercom4.o: unresolved symbol __restore_flags > > > ser_hypercom4.o: unresolved symbol unregister_serial > > > ser_hypercom4.o: unresolved symbol register_serial > > > > > > Fred > > > > > > > I can only answer for serial driver's code: > > With IOBlix driver i found a similar problem with register_serial() > > & unregister_serial() functions. > > I used m68k_register_serial() & m68k_unregister_serial() instead, > > interfacing myself with Roman Hodek's m68kserial driver and the problem > > was solved. > > This may be a quick fix for that problem, however AFAIK the m68kserial isn't > accepted by Linus and isn't in the native tree nor our 2.4 tree, which should > really be our primary development target now. There's a new amiga serial > driver - amiserial.c - in 2.4 . I think I did mention that to Fred :-) Anyway I'm working on a new driver for 2.3. This time, the hypercom1 driver is going to use the generic_serial.c code. > I'd like to have mainly only bug fixes (apart from the upgrade to 2.2.16, if > anyone really wants to do that...) in the 2.2 tree from now on. 2.2.16 supports IP Masquerading, So I would like to see that done. Kind Regards, Gordon. |
|
From: Gordon H. <go...@gh...> - 2000-07-30 19:43:49
|
Giorgio Terzi wrote: > > ser_hypercom4.o: unresolved symbol unregister_serial > > ser_hypercom4.o: unresolved symbol register_serial > > > > Fred > > > > I can only answer for serial driver's code: > With IOBlix driver i found a similar problem with register_serial() > & unregister_serial() functions. > I used m68k_register_serial() & m68k_unregister_serial() instead, > interfacing myself with Roman Hodek's m68kserial driver and the problem > was solved. Yes, but unregister_serial and register_serial are in apus_setup.c. So why don't the modules see that symbol? Kind Regards, Gordon. |
|
From: Michel <dae...@st...> - 2000-07-30 19:05:01
|
Giorgio Terzi wrote: > > fh...@at... wrote: > > > I decided to try developing my driver projects as modules in order to save > > reboot cycles. When I do this, trying to follow the module programming > > advice I got, I get unresolved symbols. How do I get rid of these? These > > symbols appear to be routines burried in the kernel various places. > > > > The Hypercom4+ module: > > > > ser_hypercom4.o: unresolved symbol queue_task > > ser_hypercom4.o: unresolved symbol mark_bh > > ser_hypercom4.o: unresolved symbol __restore_flags > > ser_hypercom4.o: unresolved symbol unregister_serial > > ser_hypercom4.o: unresolved symbol register_serial > > > > Fred > > > > I can only answer for serial driver's code: > With IOBlix driver i found a similar problem with register_serial() > & unregister_serial() functions. > I used m68k_register_serial() & m68k_unregister_serial() instead, > interfacing myself with Roman Hodek's m68kserial driver and the problem > was solved. This may be a quick fix for that problem, however AFAIK the m68kserial isn't accepted by Linus and isn't in the native tree nor our 2.4 tree, which should really be our primary development target now. There's a new amiga serial driver - amiserial.c - in 2.4 . I'd like to have mainly only bug fixes (apart from the upgrade to 2.2.16, if anyone really wants to do that...) in the 2.2 tree from now on. Michel -- Men are from Earth. Women are from Earth. Deal with it. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Giorgio T. <de...@ip...> - 2000-07-30 17:56:36
|
fh...@at... wrote:
> I decided to try developing my driver projects as modules in order to save
> reboot cycles. When I do this, trying to follow the module programming
> advice I got, I get unresolved symbols. How do I get rid of these? These
> symbols appear to be routines burried in the kernel various places.
>
> The Hypercom4+ module:
>
> ser_hypercom4.o: unresolved symbol queue_task
> ser_hypercom4.o: unresolved symbol mark_bh
> ser_hypercom4.o: unresolved symbol __restore_flags
> ser_hypercom4.o: unresolved symbol unregister_serial
> ser_hypercom4.o: unresolved symbol register_serial
>
> Fred
>
I can only answer for serial driver's code:
With IOBlix driver i found a similar problem with register_serial()
& unregister_serial() functions.
I used m68k_register_serial() & m68k_unregister_serial() instead,
interfacing myself with Roman Hodek's m68kserial driver and the problem
was solved.
Regards
Giorgio
|
|
From: Rudi C. <ru...@am...> - 2000-07-30 17:29:49
|
Hi there. I've been looking at APUS' support for Zorro Ethernet cards and it doesn't seem that encouraging. The FAQ, which is quite old, lists only the A2065, the AriadneI/II and the Hydra as supported. I was interested in getting an X-Surf, but apparently there's no driver for it. I know that it comes with full programming documentation and that it shouldn't be impossible to adapt an existing driver for Realtek chipsets, but these days time definitely isn't something I have plenty of. ;((( The AriadneII could be the second option, but the FAQ says it runs at 10% the speed of the Amiga (SANA) driver. Have things improved in the meantime? The cards also seem to be harder to find, BTW. I could look for a second-hand Hydra, but as far as I know it has only BNC and my hub only has RJ45 (and thus I'd need an expensive adaptor). Ouch. Then there's the IOBlix and its Ethernet module. The card isn't listed in the FAQ at all, but I've found in the mailing list archives that a few weeks ago a driver for the serial port(s) was added. No driver for the Ethernet module, though, so this is pretty much the same as with the X-Surf. Last but not least, the two cost roughly twice as much as the X-Surf (based on Software Hut's listings). Double ouch. And I wouldn't use the serial/parallel ports at all (triple ouch). Any suggestions? -- "A true zen saying, nothing is what I want" (Frank Zappa) Rudi Chiarito SGML/XML, user interface, i18n Amiga Inc. ru...@am... http://amiga.com/ |
107 messages has been excluded from this view by a project administrator.
