amiga explorer with amiga 1000 troubles

[zmame]

Hi,
Having troubles getting amigaexplorer getting to talk to my Amiga 1000
here is what i tryed


Bought 6' DB9 F to DB25 M Null Modem Serial cable
Specs:
6' DB9 (F) to DB25 (M) Null Modem Cable 6ft
Brand New
Specifications:

• Connector Type: DB9 Female to DB25 Male
• Designed to connect two DTE or DCE devices to one another
• Foil Shielded to prevent EMI/RFI Interference
• Fully molded with thumbscrew connectors

Also Bougt USB to COM adaptor

Have Amiga Explorer installed on PC side
Boot up Amiga with workbench 1.3
Set settings to recommended settings on amiga side
Opened Cli Typed : Type SER: to RAM:Setup
closed all extra open windows in amiga and hit enter then hit enter on PC side right after.

Says there is a problem communicating so i upped the buffer size still same problem persists. I checked setting made sure it was in COM 3 (only option) bit rat 19200 packet size 512.

Tryed on a older PC i had running windows 98 still same problem.

Also tryed reducing colors, trying in shell insted of Cli and nothing seems to work. Any ideas what im doing wrong?

[prowler]

Hi zmame,

You must feel very disappointed, having heard here how Amiga Explorer is such a great application.

To get Amiga Explorer working properly between your Amiga and PC, the null modem cable has to conform to the specification given on the Amiga Forever website.
http://www.amigaforever.com/kb/13-105



DB-25 connectors on both ends



DB-9 connector on one end; DB-25 on the other end

Threre are a couple of variations of null modem lead, so check that your cable conforms to this specification.

[ppill]

What version of serial.device you're using? Type 'version serial.device' in a shell window and post the result.

Some versions have problems with that transfer trick used by AmigaExplorer.

[zmame]

Originally Posted by ppill

What version of serial.device you're using? Type 'version serial.device' in a shell window and post the result.

Some versions have problems with that transfer trick used by AmigaExplorer.

It's Version 34.10

[ppill]

Originally Posted by zmame

It's Version 34.10

Yeah, that might be it. Version 34.70 works best for 1.3 kickstart.

Info from here: http://adfsender.stoeggl.com/faq.html

[zmame]

Originally Posted by ppill

Yeah, that might be it. Version 34.70 works best for 1.3 kickstart.

Info from here: http://adfsender.stoeggl.com/faq.html

I guess ill stick to amigaforever emulator this whole thing is making my head sore Ill just save up and get a 1200 down the road if i can find one.

It's hard to find amiga stuff in canada.

[ppill]

Originally Posted by zmame

I guess ill stick to amigaforever emulator this whole thing is making my head sore Ill just save up and get a 1200 down the road if i can find one.

It's hard to find amiga stuff in canada.

I think there are few users from Canada here. You might what to ask if someone would be willing to send you a disk with a compatible version or maybe a Hombre disk (check my sig for more details).

Hi!

I have a PC db25 to db9 null modem cable. But I think it's
just a regular pc null modem cable (it prolly doesn't have the
same specs as the one on amiga explorer). Can I convert this
cable? Is there somewhere in the USA that sells these amiga
to pc null cables? I am using an Amiga 1000.

Also, if I type 'type ser: to ram:test' with or without
a null modem cable (the non amiga one) it locks and I cannot
control-c or stop it (same with 'copy ser: to ram:test').

Any and all help is appreciated!

Thanks,
John

[prowler]

Originally Posted by JohnnyL

I have a PC db25 to db9 null modem cable. But I think it's just a regular pc null modem cable (it prolly doesn't have the same specs as the one on amiga explorer). Can I convert this cable? Is there somewhere in the USA that sells these amiga to pc null cables? I am using an Amiga 1000.

Hi John,

You should indeed be able to convert this cable provided you have a soldering iron and the connectors are not of the moulded (encapsulated) type.

[Hewitson]

In my opinion it's very unlikely the cable is the problem. More likely to be the USB to Serial adapter, I suggest testing on a system with a real COM port.

[ppill]

Originally Posted by Hewitson

In my opinion it's very unlikely the cable is the problem. More likely to be the USB to Serial adapter, I suggest testing on a system with a real COM port.

Have to agree, null-modem cables are pretty straightforward. You can check with a multimeter if all the necessary pins are connected. Some USB2Ser adapters don't support all the required signals.

Also you need to send another file after CTRL+C for the shell task to break.