| Re: ADTPro Issue [message #399245 is a reply to message #396951] |
Fri, 04 September 2020 09:18   |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
ADTPro works with 32MB hard drive images. I've done it plenty of times before.
This setup worked up until quite recently. I was able to transfer hard drive images (and floppy images) to my IIgs and IIe without issue. This problem is new, so it's probably not an ADTPro issue as ADTPro hasn't changed in a long time.
I'm thinking this might be related to my router. I had to get a new router a few months ago, but I *thought* it was working under the new router. It's hard to remember the last time I had ADTPro working and when I got my new router. I'm using DD-WRT on my router, so maybe there's a setting that ADTPro doesn't like? I searched through my router logs and saw this error two of the three times the transfer failed. Not sure if it's related though (Atari-Router in my router's name BTW):
>> Sep 4 09:08:26 Atari-Router daemon.err httpd[1265]: httpd : Request Error Code 408: No request appeared within a reasonable time period
If it's not the router, my only other guess is that something went bad with the Uthernet I card. I find this hard to believe though because it still works on smaller files. You'd think that if something was wrong with the card then nothing would work.
|
|
|
|
| Re: ADTPro Issue [message #399246 is a reply to message #399244] |
Fri, 04 September 2020 09:27 |
David Schmidt
Messages: 994
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 9/4/20 8:39 AM, Jeff Blakeney wrote:
> On 2020-09-03 2:26 p.m., Tempest wrote:
>> It's an Uthernet I BTW. It *does* work with small files (5.25" disks
>> and usually 3.5" disks), but anything large like a hard drive file it
>> will fail. The problem seems to manifest itself after a short time,
>> but small data transfers are ok.
>
>
> As far as I know (I've never used it) ADT is a ProDOS 8 application and
> therefore only works under ProDOS 8. ProDOS 8 has a maximum file size
> of 16 MB so if you are trying to transfer a 32 MB hard drive image (or
> anything over 16 MB), it won't be able to fit on your local ProDOS 8
> partition. That would be why it works for smaller files but not larger
> ones.
ADTPro doesn't transfer individual files, it transfers disk images in a
series of chunks. A 32MB drive is chunked up and sent a piece at a
time, reconstituted on either end of the wire, depending on which way
it's going. So file size isn't at issue here; it's networking.
|
|
|
|
| Re: ADTPro Issue [message #399251 is a reply to message #399246] |
Fri, 04 September 2020 09:56 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
>> So file size isn't at issue here; it's networking.
Yes, at this point I'm 99% sure it's a network issue. However I have no idea where to start looking for issues or ever what could be causing them. Something with my DD-WRT settings on my router obviously, but what? Perhaps if we can narrow down the potential possible causes I can figure it out? DD-WRT has a lot of customizable settings. Too many honestly, much of it is above my head.
|
|
|
|
| Re: ADTPro Issue [message #399261 is a reply to message #399251] |
Fri, 04 September 2020 14:20 |
|
|
Originally posted by: Bobbi
Can you borrow a router? Would be interesting to swap it and see what happens.
Bobbi
On Friday, September 4, 2020 at 9:56:04 a.m. UTC-4, Tempest wrote:
>>> So file size isn't at issue here; it's networking.
> Yes, at this point I'm 99% sure it's a network issue. However I have no idea where to start looking for issues or ever what could be causing them. Something with my DD-WRT settings on my router obviously, but what? Perhaps if we can narrow down the potential possible causes I can figure it out? DD-WRT has a lot of customizable settings. Too many honestly, much of it is above my head.
|
|
|
|
|
|
| Re: ADTPro Issue [message #399477 is a reply to message #399262] |
Mon, 07 September 2020 13:25 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
|
Turns out I do have an old router (a DIR 655) that I was able to try out. I get the same issue. This router is stock with no custom firmware and I do remember it working with ADTPro back when I used it. At this point it's either got to be the card or possibly my modem. Those are the only two things left to check, I've changed out everything else!
|
|
|
|
| Re: ADTPro Issue [message #399641 is a reply to message #399477] |
Tue, 08 September 2020 22:16 |
|
|
Originally posted by: Delfs
On Monday, September 7, 2020 at 12:25:31 PM UTC-5, Tempest wrote:
> Turns out I do have an old router (a DIR 655) that I was able to try out. I get the same issue. This router is stock with no custom firmware and I do remember it working with ADTPro back when I used it. At this point it's either got to be the card or possibly my modem. Those are the only two things left to check, I've changed out everything else!
Have you considered you ADT maybe bad? Maybe start with a fresh copy of that. -Ed
|
|
|
|
| Re: ADTPro Issue [message #399642 is a reply to message #399641] |
Tue, 08 September 2020 22:30 |
|
|
Originally posted by: Bobbi
Firewall settings is something else to check.
Bobbi
On Tuesday, September 8, 2020 at 10:16:26 p.m. UTC-4, Delfs wrote:
> On Monday, September 7, 2020 at 12:25:31 PM UTC-5, Tempest wrote:
>> Turns out I do have an old router (a DIR 655) that I was able to try out. I get the same issue. This router is stock with no custom firmware and I do remember it working with ADTPro back when I used it. At this point it's either got to be the card or possibly my modem. Those are the only two things left to check, I've changed out everything else!
> Have you considered you ADT maybe bad? Maybe start with a fresh copy of that. -Ed
|
|
|
|
| Re: ADTPro Issue [message #399666 is a reply to message #399642] |
Wed, 09 September 2020 09:48 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Re-downloading ADTPro was the first thing I did. Same issue.
I can look into the firewall possibility, but if it was the firewall you'd think that absolutely nothing would work. Firewalls are generally all or nothing. Also I don't think that other router I tried had a firewall enabled. Still, something to look into.
At this point I'm thinking that my Uthernet card might be damaged somehow. Is there anything on the card that could get damaged but still allow it to function partially? Like I said, it works for short transfers still.
|
|
|
|
| Re: ADTPro Issue [message #399740 is a reply to message #396951] |
Thu, 10 September 2020 08:00 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
While ordering an Uthernet II card I noticed the manual had a quick test you could run. I'm not sure if this is specific to the Uthernet II or if it will work with the original card so I tried it and got this result:
*C094: 80
*C094: 03
*C094
00/C094- 09
According to the manual I should get a 03 not and 09 back. Like I said, I don't know if this test is valid for the original Uthernet or not, but I thought I'd post the results here in case they're useful.
|
|
|
|
| Re: ADTPro Issue [message #399782 is a reply to message #399740] |
Thu, 10 September 2020 14:12 |
|
|
Originally posted by: Bobbi
I am not sure what that test does exactly -- writes to C094 twice then reads back ... Pretty sure it would be specific to Uthernet-II though.
Aside from the fact that both Uthernet and Uthernet-II are Apple ][ cards and have an Ethernet connector they are quite different in terms of implementation. Don't be fooled by the similarity of the names.
All the best,
Bobbi
On Thursday, September 10, 2020 at 8:00:13 a.m. UTC-4, Tempest wrote:
> While ordering an Uthernet II card I noticed the manual had a quick test you could run. I'm not sure if this is specific to the Uthernet II or if it will work with the original card so I tried it and got this result:
>
> *C094: 80
> *C094: 03
> *C094
>
> 00/C094- 09
>
> According to the manual I should get a 03 not and 09 back. Like I said, I don't know if this test is valid for the original Uthernet or not, but I thought I'd post the results here in case they're useful.
|
|
|
|
| Re: ADTPro Issue [message #399804 is a reply to message #399641] |
Thu, 10 September 2020 14:15 |
|
|
Originally posted by: Delfs
On Tuesday, September 8, 2020 at 9:16:26 PM UTC-5, Delfs wrote:
> On Monday, September 7, 2020 at 12:25:31 PM UTC-5, Tempest wrote:
>> Turns out I do have an old router (a DIR 655) that I was able to try out. I get the same issue. This router is stock with no custom firmware and I do remember it working with ADTPro back when I used it. At this point it's either got to be the card or possibly my modem. Those are the only two things left to check, I've changed out everything else!
> Have you considered you ADT maybe bad? Maybe start with a fresh copy of that. -Ed
Did you try using a hub instead of a switch? Did you try a cross over cable to hook the source machine to your Apple?
|
|
|
|
| Re: ADTPro Issue [message #399852 is a reply to message #399804] |
Fri, 11 September 2020 09:39 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
> Did you try using a hub instead of a switch? Did you try a cross over cable to hook the source machine to your Apple?
No, but I did hook it directly to my router, bypassing the switch entirely. I don't think I have a crossover cable here at home, I'll have to borrow one from the office next time I'm in.
|
|
|
|
| Re: ADTPro Issue [message #399853 is a reply to message #399782] |
Fri, 11 September 2020 09:40 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On Thursday, September 10, 2020 at 2:12:26 PM UTC-4, Bobbi wrote:
> I am not sure what that test does exactly -- writes to C094 twice then reads back ... Pretty sure it would be specific to Uthernet-II though.
Is there a list of all the differences between the two? I'm curious now. I assumed that the II was just an upgraded version of the original.
|
|
|
|
| Re: ADTPro Issue [message #399863 is a reply to message #399853] |
Fri, 11 September 2020 11:16 |
David Schmidt
Messages: 994
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On 9/11/20 9:40 AM, Tempest wrote:
> On Thursday, September 10, 2020 at 2:12:26 PM UTC-4, Bobbi wrote:
>> I am not sure what that test does exactly -- writes to C094 twice then reads back ... Pretty sure it would be specific to Uthernet-II though.
>
> Is there a list of all the differences between the two? I'm curious now. I assumed that the II was just an upgraded version of the original.
The list is: everything. It's a new chipset, a new programming
interface, and everything in between. The only thing they share is the
name.
|
|
|
|
| Re: ADTPro Issue [message #399864 is a reply to message #399863] |
Fri, 11 September 2020 11:34 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
> The list is: everything. It's a new chipset, a new programming
> interface, and everything in between. The only thing they share is the
> name.
Ah ok, I guess it's time to upgrade. :) At this point I'm pretty sure my Uthernet card is just broken somehow, it's the only thing that makes any sense. Maybe some stray voltage or something zapped it? Who knows.
I gave it one last test after updating my router's firmware. It still fails after a bit with the ACK errors but it doesn't do that weird 'halting/chugging' thing it used to do. What I mean by that is that the transfer bar would halt for a second then resume but it would keep doing that and eventually fail. Now it keeps going at the smooth fast speed you'd expect, but then it randomly fails and aborts. I really thought it was working all the sudden, but alas.
>> 9/11/20 11:28:31 AM CommsThread.sendPacketWide() Ack received for block 12515, but we were expecting an ack for block 12513.
|
|
|
|
| Re: ADTPro Issue [message #400584 is a reply to message #399864] |
Sat, 26 September 2020 15:04 |
Tempest
Messages: 529
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
|
I got my Uthernet II today and it works perfectly. So the problem is with my Uthernet I card itself. I've inspected the card and everything *looks* ok, but I'm not sure how to diagnose it further. There don't seem to be many components on the board itself, is there any one in particular that I should inspect/replace that might cause a problem like this?
|
|
|
|
Members
Search
Help
Register
Login
Home
