The methods A and C were developed for people who only own an Amiga with the Workbench disk.Ĭheck that the serial settings are the same on both machines (e.g. Amiga 600, Workbench 2.05 and higher)ĭue to the feedback I get, most people prefer method B. Amiga 500, Workbench 1.3, Extras)Ĭ With ARexx script (e.g. Especially for TransWarpī With AMIGABASIC (e.g. A2 TYPE command and self extracting archive. The file is sent to RAM: of the Amiga, which should prevent transmission errors.Ĭhoose method A, B or C: A You only need a Workbench disk or at least the TYPE command on the AMIGA (Amiga with Workbench 1.2 or 1.3) The given examples refer to transdisk, but you may want to transfer TransWarp, twinexpress or dos2dos etc. (Yes, I am serious - people ask me things like that.) Press Ctrl+D while booting the Workbench or start 'shell' from the Workbench, which has got advantages under kickstart1.x as you can repeat commands with the cursor keys. On the Amiga commands are entered from CLI or shell.
If you want to change the serial settings you have to start preferences on the Amiga Workbench or properties within ADF Sender Terminal on the PC. I highly recommend using RTS/CTS handshaking.
AMIGA EXPLORER SERIAL SETTINGS HOW TO
This page has been released because people have asked me how to exchange files between Amiga and PC without a terminal program, CrossDOS,Īll methods described require a nullmodem cable and ADF Sender Terminal.Ĭlick here to see the schematics under 3.).
Something to mull over.Amiga - PC first steps New, simplified methods to get the FIRST file but that 'e on A1000 version' was niggling at the back of my head, what's that all about?. I assumed the '0 Motherboard memory' was just telling me that it couldn't find any memory, and started to think about how to debug this further. The message that the 'Garbage' before the text is for debugging bit errors to Paula makes sense (And had this not been the first time I'd used DiagROM, might have sped up my earlier data bus fault finding!), but what's this odd message: 'e on A1000 version' all about? I didn't think the author of DiagROM, John "Chucky" Hertell was from Yorkshire in the north of England!?. I'm getting some useful text on the serial port now (still nothing out the video port), but clearly something is still off. Nothing.I try a Ctrl + A + A and I'm greeted with this out of the serial port: This site proved invaluable in tracing down opens)Īfter the quick patch-up I hit the power switch again. (Huge shoutout to the maintainers of from which the above image was captured. but for future reference, the red marks below show exactly where the breaks were: I'd later go back and do a proper repair on these. Sure enough, I found that DRD_27 and DRD_20 were open somewhere between Bridgette and Paula.Ī couple of (temporary!) bodge wires were duly installed to make the connection. So, I turn my attention to the data bus, focusing on the bits that go across to Paula (DRD_31 - DRD_24). That's somewhat good news, in that it tells me that the CPU is at least alive enough to be sending something across to the custom chip Paula to spit out the serial port. But when I tried a "Ctrl + A + A" keyboard reset, I'd get a bunch of uninteligable garbled characters out of the serial port: I wasn't seeing anything when I powered on. With the A4000 Serial port connected with a jury-rigged null modem cable. nothing on screen, but could I see anything on the serial port? (DiagROM talks on the serial port as well as trying to display to the screen.) So it was out with Kickstart, in with DiagROM and power on. Certainly nothing glaringly obviously broken. Other than the PCB trace damage and pad damage to U977 around the battery with attempted bodge wire fixes, it wasn't looking *too* bad.
0 kommentar(er)
