Okay, this topic has been beaten to death, and I must give others credit where due, but I believe this is the answer for all of those who wish to have a simple solution with their winmodems. No more dialing out to the ISP, for anything, zero fears with netpliance messing with things. Feel free to reply and give yourself credit where due for establishing this hack. Now onto getting the job done, quick and dirty.
Download Power Terminal Pro onto your windows PC from Tucows:
http://tucows.revealed.net/files5/Ptprose.exe
Forget using HyperTeminal. Some have reported success, however I got nothing but errors. Power Terminal Pro is much more straightforward, and has the option we want right in front of our eyes. It doesn't get much better than this. Install the program and away we go.
If you already have a root shell established, you can ignore this part. Power on the IO, and let it go through the tutorial far enough that it wants user input. If you've attempted to do the ISP hack, you're probably getting a "Please wait while I-Opener updates" screen. This being the case, let your IO stand untouched for a few hours. I'm not kidding, the thing will be trying to update itself every so often for many, many hours. I let mine stand untouched for a few days when I did this. This is much worth your time. Upon reaching this point, regardless of your situation, hit the number 4 5 times. (I've read esc-4, but 4 works fine for me), and type "login root", and "osiw$6.4", to get root access. Go to /dbin, and type "qtalk -m /dev/modem".
Once into qtalk, type the following sequences:
atz
at#cw0
at#cwt6
atx1
atdt1
DO NOT hit enter after you type atdt1. Also note, other posts have indicated to type ata here, however after trying three winmodems, I can verify that this method is more reliable. Now let's move back to the PC. Start up powerterm, and you will be prompted for connection type. Choose COM, and make sure you pic your com port to right right after the menu flashes over. In my case I was on COM 3, and right above that you can choose your connection speed, I chose 38.6. Hit okay and you should now have an open connection to your modem. Type:
atz
atx1
ata
Hit enter now on the IO, then on the PC. Connection!
Now hit ctrl-a, x on the IO to bring you back to a prompt without disconnecting.
cat /dev/modem> rawfile.tgz
hit enter and leave it be, go back to the pc and click Communication/Send File...
Choose your file at the prompt, set your protocol to Binary, and click Options>>, and here is the key to success. Choose 7-bit for both sides, and click Send! Now wait a good while for the transfer to complete (I've tried to find a way to "echo" the transfer onscreen so you have some idea as to status, but haven't done so successfully yet) and then hit ctrl-c on the io side, and type ls -l rawfile.tgz to see the length of the file, right click and hit properties on the file you sent on the windows box and compare. They should be painfully close to the same. (Note: the .tgz extension is presuming that you're sending a gzipped tar file as described in another post) Now pipe the file through gzip like so:
cat rawfile.tgz | gzip -d > rawfile.tar
you will get one of two responses here more than likely. Unexpected end of file, which ironically is a good sign, or bad crc, doesn't look like a gzip'ed file...type ls to get a listing of the files in /app/ztest. If a rawfile.tar is there, you're halfway to being home free.
tar -xvf rawfile.tar
ls again. If your files made it through, you're set.
Now, I concur with everyone else that you should indeed send through the RZ command with some padding using this method. That is what I did. Read the other post about this
http://www.linux-hacker.net/cgi-bin/UltraBoard/UltraBoard.pl?Action=ShowPost&Board=verytech&Post=55&Idle=0&Sort=0&Order=Descend&Page=0&Session=
Once you get RZ through and transfer it to /dbin, two things. ONE, remember to chmod 755 rz, and TWO, the method to use zmodem in qtalk is ctrl-a, t, zmodem, ctrl-a, r. This will give you a response telling you to use sz on the remote terminal. DO NOT USE Power Terminal Pro to send via ZMODEM! Apparently one of the limiting features of this shareware release is a certain number of bytes may be sent using zmodem. Switch back to HypterTerminal using the same method to send everything else across using zmodem.
That should be about it. Kudos to everyone who has worked on this. I believe now that we have an airtight way to send files across using a windows box, there should be no more use for ISP hacking to flash the bios. ;)
Numbski
