phils@tekigm2.TEK.COM (Philip E Staub) (09/07/87)
[wonder what would happen if I put something *really* important here?] Several months back I posted a patch for the Amiga Transformer to allow it to run under Workbench 1.2. I've received enough "attaboys" that I've decided to try to out-do myself. There were three major areas which the original patch did not address, or did not address them in ways I felt comfortable with: 1. The original patch would allow Transformer to be used with WB 1.2, but you could not go back to 1.1, and presumably another patch would be necessary if (when?) 1.3 comes out. 2. The original patch was done with no expansion memory, and has been shown later to not work particularly well with it. 3. The original patch did not address the issue of 68000/68010 incompatibility. Well, after a fair bit of, well, let's face it, hacking, I've been able to come up with another patch which I think will solve all three of the original patch's shortcomings. The problem is that I do not wish to waste net bandwidth with a program which is not reasonably well debugged. At this time, the only expansion RAM I have is the extra 256K you get with the Kickstart Eliminator. While the new patch appropriately handles this memory, I hardly consider it to have had a full test unless I can get a few kind souls to try it out with some other types of expansion RAM. (BTW, points 1 and 3 above have been reasonably well tested and I believe the problems to have been solved). So here is the question: Do you have a) some expansion RAM, b) Amiga Transformer, and c) a C compiler, and would you be interested in testing my new patch? If the answer to all of the above is "yes" I'd like to hear from you (preferably via e-mail, of course). I'd like to pick some representative types of expansion RAM (please let me know whether it's auto-config or not) and someone with both the Lattice and Manx C compilers. (BTW, I'm using Manx 3.40a, so I'm reasonably sure it will work with that one). (Of course, if anyone from C-A would care to try it with WB 1.3, I'd appreciate that, too ;-) ) Then, when I'm satisfied that all is well, I will be posting the new patch to both the sources and binaries newsgroups. Thanks in advance. Phil -- ------------------------------------------------------------------------------ Phil Staub "I do NOT approve. I merely said I UNDERSTAND." tektronix!tekigm2!phils - Spock phils@tekigm2.TEK.COM
rob@ccubed.TNET (04/15/88)
[Warning ... Semi-Commercial Posting]
Hi all,
I need Beta testers for a program my company getting ready to release.
It is not a glorified terminal program but a true communications
package it does everything UUCP can do but with almost ANY system at
the other end. It runs protocol and terminal emulations like Deluxe
Music (tm) plays scores. Can be used with any device (some 'C'
knowledge required), defaults to the serial port. Complete comm
language including vars, loops, tests, auto-menu strips, requesters,
screen control (32/64 colors, # bit planes, proportional fonts,
multiple fonts and keymaps, std clear/pos cmds). Only uses the device
when the comm channel is active. Capable of completely unattended
operation through use of a full-blown auto-connect system (can respond
differently to multiple stimuli -- thus you can handle a wide variety
of error/status conditions). It is not a memory hog (runs fine
on a 256K A1000 & only uses about 1/2 of it). Oh, BTW you can (if
you really want to) use it like a terminal program.
I have general use Beta testers and now I need people to test the docs/
includes/code that allows people to easily implement their own
protocols. The design of the program makes it relatively easy to
convert public domain protocol code into a form usable by the program.
I am not sure how much work this involves -- it would take me about 2
days per protocol (but I know the system). Keep in mind that ONLY the
protocol must be ported, everything else (physical channel management,
user interface, protocol debug code) is already present.
I will take those who have written PD protocol codes previously for
the Amiga over others since they can use their own code and are thus
familiar with it.
I may need Beta testers for the terminal files too, but the general
use beta testers (non-hardcore programmers) seem to have little
trouble implementing terminals using the universal terminal emulation
(UTM) code.
Please respond to: ...!burdvax!aspvax!gateway OR
...!sun!liberty!drexel!aspvax!gateway
with the Subject : Beta Test
Thanks,
"You and I are scientists professor, Rob Ginn
we buy our right to experiment at ...burdvax!jtids!aspvax!eraps2
the cost of total responsibility" ...sun!liberty!drexel!aspvax!eraps2
-- The Doctor eraps1@nadc.arpabobb@agora.uucp (Bob Beauchemin) (07/18/90)
...We are looking for beta-testers for the Open Look window manager (OLWM) for the Amiga. This is a "window manager" program that runs under X11 for the Amiga from GfxBase, and provides the XWindows/Amiga environment with an OPEN LOOK(TM) kind of "look-and-feel". Ownership of X11 for the Amiga, release 3.1, by GfxBase, is a pre-requisite. Send e-mail inquiries to: bobb@agora.hf.intel.com Also enclose your GfxBase customer number (required), and a description of your network configuration. If you are interested in X11 for the Amiga (an optimized XWindow server and clients that run under native AmigaDOS, and allows Amiga/Intuition and XWindows programs to run concurrently), contact: GfxBase 1881 Elwell Drive Milpitas, CA, 95035 (408)-262-1469 OPEN LOOK is a trademark of Sun Microsystems, Inc and AT&T THANKS, ...Bob Beauchemin S&B Software, Inc 6503 SW 46th Place Portland, OR, 97221 (503)-244-5029