Amiga Explorer - Install Help

[Kernel]

Anyone know how to get by the attached error?  I thought my OS was hosed (Vista Home Premium x64) so I reformatted and installed Windows 7 Enterprise x64 and I'm still getting the same problem.  I sent a log to cloanto at their request yesterday and I'm still dead in the water.

[Kernel]

Yep... since I installed all updates, I'm at win 7 SP1 so I tried

Win 7
Win Vista
Win Vista SP2
Win Vista SP1
Win XP SP2
Win XP SP3

[Kernel]

I have a key for 2009 and it's supposed to be valid for Windows 7 which is why I'm not moring on the newest yet.

EDIT: Hmmm... I didn't realize that Amiga Explorer keys are usable on newew versions.  I'll try that.

[Kernel]

Ok, 2010 version working fine!  Copying 20MB via 19,200 baud brings back memories LOL.  I forgot to up the rate but I do have a 219MB partition to copy as well so will up the rate for that one before I start it.

The 20MB has been going for about 2 hours now and is about 1/3 done... Windows says about 3 hours and 15 minutes remaining.  We all know how reliable Windows is in that department though.  Ha it just jumped to 2 hours and 55 minutes.


Thanks for that last suggestion.  I guess I just assumed Amiga Explorer was tightly bound to the version of Amiga Forever you were licensed for.  Geesh - support didn't even recommend I try the latest version!

[Kernel]

I'm starting to lose faith on this method for file transfer.  I understand that there are many moving pieces when doing something like this... a 20+ year old computer, serial to USB dongle, null model cable that may or may not be considered "good quality" - but being able to transfer 20MB without problem over the cable and then to all of the sudden have COM PORT write errors on the Windows side just doesn't give me a good feeling.  I even wonder if the files that did transfer were really a 100% success.

So here it is:

I have the 2.53GHz Windows  machine with a Trendnet Serial/USB dongle to a 10ft 9F to 25F NULL cable.  COM4 is set to 19200, 8-N-1, Hardware Flow,  and the transmit and receive buffers have been set to 4 (it indicates lower settings help with connection issues).

The serial prefs on the amiga are RTS/CTS, 8-N-1, 19200, and 8192 for the buffer.  In the AE icon, I have it set to 19200 with 1000 retries.

Can anyone suggest a resolution other than "must be a bad cable dude" becaue I just can't buy that in this day and age.

[Kernel]

Sorry, 25MHz A3000.  2MB Chip and 16MB Fast.

Fresh load of OS 3.1 just now too and still the same problem - and that was fun let me tell you... I forgot I didn't have a fonts disk and had to scramble and piece together a CrossDOS installation so I could transfer a fonts adf to it and create the disk - all the while the installer was waiting for the fonts disk to continue!  Talk about trying to remember commands like "assign add" to make a crossdos mount after 10+ years of being away from the Amiga... LOL.

I got AE transferred and running in the machine again and it doesn't lock up like it did before when trying to shut it down and change settings for baud, but the same issue happens on the PC side.  It will sometime upen but more than likely, it will error out.

I want to get it running over NULL but I'm probably just gonna give up and put the DENEB in and hook up the NIC dongle and forget about it.

[Kernel]

Well, it *appears* that the 38400 setting is holding.  It's been copying the 219MB partition over the to PC since approximately 9PM EST last ngiht and it's now 1:40PM.  It says it has 10 hours left .

Would increasing the "retries" have any affect on the "unable to write to COM" errors?  By the looks of it, with this clean install, it would happen when initially clicking on the AE icon or trying to click into one of the drives.

[Kernel]

Well, I've the the A3000 up on TCP with the DENEB and can ping back and fourth, and the AmiTCP log indicates thah it's leeting traffic in on the required port, but the PC gives TCP errors when trying to do anything,

[Kernel]

Both hard wired into my router.  Thr AmiTCP log pops up saying it accepted the connection on 356 but then on the PC side I get the error.  I'll try clearing the passwords.

Next step is upgrading the stack that came with EasyNet.  I have OS3.9, just have not installed it yet.  I can get Miami also of course.

[Kernel]

Ok, I got MiamiDx installed and am having slightly better results... AE no longer acts like it obtains then immediately drops the connection however when trying to copy one of the partitions over to the PC, I receive a timeout on the "retrieving folder information" popup.

I left the settings in AE to utilize bdsocket.library but perhaps there is a different library I should be using that is miami based?  I have packet size at 32768 right now and my retries are at 1000.

I definately need to sit down and refresh my memory by groing through guides and such.