root@sbcs.UUCP (SBCS Systems Staff) (02/25/86)
If anyone out in NetLand has sample driver and/or handler code, I would greatly appreciate the gesture if you would send me a copy of your source(s). Thanks, Rick Spanbauer SUNY/Stony Brook
jcz@ncsu.UUCP (John A. Toebes, VIII) (02/27/86)
I have a driver that is designed as a replacement for the PORT-HANDLER driver. In constructing it I had to disassemble the PORT-HANDLER one and figure out exactly what the conventions are. Unfortunately because the original one is Commodores and I have not yet been allowed to talk to Dave Street (Is he too busy for us lowly developers interested in advancing the machine?) so that I could get permission to post it. With my version that I have rewritten from scratch, I have a module that is half the size of the original and works 99.99% of the time. Apparently there is one unknown convention of BCPL code that I have not decifered and am not following. In talking to Commodore west cost I was promised, but never received any information that might help resolve the problem. What it boils down to is even my rewrite works a large portion of the time, blowing up only *AFTER* it is no longer in use. I will make one last attempt to contact Commodore, failing that I will go ahead and post my own version of PORT-HANDLER and hope for the best. Also, if enough interest exists I will post everything I have determined about the restrictions and conventions imposed by the BCPL environment for AmigaDos device drivers (note that the example in the new 1.1 Vol2 Rom Kernal manual is in BCPL, cannot be translated to C sue to the environment conventions and as such is useless) Commodore, are you listening? How can people develop software if the information isn't given out? John A. Toebes, VIII 120 H Northington Place (where Amiga Hack comes from) Cary NC 27511 (919) 469-4210 ...mcnc!ncsu!jcz Standard disclaimer: My amiga wrote the above on its own.