CompuServe Messages

David. I take it you are a reviewer for CADalyst… Always glad to make the acquaintance of someone with the same mindset. I'm a Byte reviewer (when on assignment) and have worked in the animation field since the early days of Targa/Crystal/Topas. (Wrote the 3DS rel 1 review for last year's Byte – April 91). Just finished up a piece for the June 92 issue and touched briefly on the topic of local bus video also. (There's lots of LBV standards on the horizon… I'm waiting for VESA to establish some guidelines before I `jump in' head first with a new system). While I've got you on-line, perhaps I might ask a question regarding 3DS rel 2 RDPADI configurations. I've tested it with the both a Targa+ 24 and an AT-Vista board. However, for grins, I threw in the old Targa 16 to check out the new rdptarga.exp driver (this was mainly to verify that I could send NTSC straight composite out at 512×482 directly to a Sony VO-5850 3/4" VTR, thusly bypassing the RGB/NTSC encoder box). This was for readers who don't have an encoder and pull sync directly off the Targa 16. I'm getting all sorts of strange characters in popping up in the main 640×480 editor display when I start 3DSr2. This method worked great in 3DSr1. (I have set the .exp environment paths correctly… i.e. set rdpadi=d:\3ds2\drivers\rdptarga.exp). Any suggestions (from one and all) would be appreciated. I've also used the trueinit Targa setup utility to change memory addresses of the T16 adapter, but have had little success. Thanx in advance for any guidance. BTW: Pardon my grammar and spelling in the above… I get dyslexic after staring at a crt for 18 hours <g>. – Greg Loveria