Subject: Re: HELP HELP HELP ADT122-- a new adt.dmp Path: lobby!newstf02.news.aol.com!portc05.blue.aol.com!newsfeed.direct.ca!newsfeed.mathworks.com!cyclone.swbell.net!news.swbell.net.POSTED!not-for-mail Message-ID: <38985435.57526191@swbell.net> From: Rubywand Reply-To: rubywand@swbell.net X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.sys.apple2,comp.emulators.apple2 References: <38976FCC.5D5F5C9C@ajba.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 80 Date: Wed, 02 Feb 2000 09:58:45 -0600 NNTP-Posting-Host: 209.184.83.204 X-Complaints-To: abuse@swbell.net X-Trace: news.swbell.net 949507173 209.184.83.204 (Wed, 02 Feb 2000 09:59:33 CST) NNTP-Posting-Date: Wed, 02 Feb 2000 09:59:33 CST Organization: SBC Internet Services Xref: lobby comp.sys.apple2:94820 comp.emulators.apple2:19664 "Avram J. Berman" writes ... > > I got my dos 3.3 master disk and booted it up and typed in#2 and then > control a and got the ssc: prompt and then typed 6b for 300 baud - that > was simple. I set the dip switches on the super > serial card according the the adt122 documentation, using a null modem > cable - that was simple. > > At the dos prompt I typed in: > mode com1: baud=300 data=8 parity=n > and then > type adt.dmp >com1: > > "yes I am in the right directory with the right path to adt.dmp > I get the message, "write fault error writing device 1. Does this mean > the problem is on the pc side or the apple?" .... Did more checking (since an earlier post which somehow got a 12PM time stamp). First, in the mode command, MS-DOS doesn't care whether you say "baud=300" or "baud=30". (It uses only the first two digits to pick baudrate. If you say "baud=300" it ignores the extra 0 and sets baudrate at 300.) One way to tell if the mode command takes is that you should get a response of something like COM1: 300,n,8,1,- after entering the mode command (for COM1 in this example). Delfs's method works for sending the adtgs.dmp file because adtgs.dmp uses only a CR character (ASCII $0D) to end lines-- i.e. a standard Apple II line ender. The adt.dmp file in 8-bit ADT uses CR and LF (ASCII $0D $0A) to end lines. This is the usual PC line ender. When sent via a telecom program (like HyperTerm) which can screen out the LF's, there is no problem. However, the LF's get through when adt.dmp is sent via the MS-DOS command type adt.dmp >com1: and the LF's mess things up on the Apple II end. Since Delfs's approach is a lot simpler than fiddling with HyperTerm, there is a new adt.dmp file which uses only CR's to end lines (like adtgs.dmp). The new dmp file is named "adtn.dmp". It is included in the .zip file ADT122nudmp.zip currently in the early preview Feb 2000 issue of GS WorldView at ... http://www.grin.net/~cturley/gsezine/GS.WorldView/v2000/Feb/ADT/ . After downloading, use WinZip or a similar utility to unzip ADT122nudmp.zip. ADT122nudmp.zip has, so far, also been uploaded to Ground, ACN Tarnover, and Asimov. Whether or not the new ADT dmp file will completely solve your transfer snag is hard to say. In tests, it transferred fine using Delfs's MS-DOS commands-- also faster, about 4.5 minutes at 300 baud. (You can get some idea if the transfer is working by watching what gets 'typed-in' on the Apple II screen during the transfer. It should look like someone typing hex code.) The install directions mention that can set the SSC to "Terminal" and remove the NULL modem adaptor from the connection. You might give this a try. If you do not get any response when entering the mode command (or, you get an error message), the problem may be your version of MS-DOS or with the kind of PC you are using. (There may be some other way to set up a COM port on your computer.) Otherwise, if the direct approach does not work, you may have to go ahead and use a telecom utility on the PC to send the file. Rubywand