> The thing is, all recent ComOS releases ARE NOt BINARY FORMAT.
You sure about that?
[root@tarkin data]# file *
pm2_3.1.4: WE32000 COFF executable N/A on 3b2/300 w/paging 32100 required
pm2_3.3.3: PDP-11 old overlay
pm2_3.5: PDP-11 old overlay
pm2_3.7: PDP-11 old overlay
> You can transfer them NOT in binary mode - that's the point of having them
> in a uuencoded form now. There is no worry over making sure it is sent
> in binary mode.
They don't look like any uuencoding I've seen. Also, xfering them in
ascii mode alters the size:
The first was ftp'd in ascii mode, second in bin mode.
-rw------- 1 jlewis users 280595 Aug 13 22:12 pm2_3.7
-rw------- 1 jlewis users 396314 Aug 13 22:12 pm2_3.7.bin
yoda:~$ file pm2_3.7*
pm2_3.7: PDP-11 old overlay
pm2_3.7.bin: PDP-11 old overlay
yoda:~$ md5sum pm2*
b8bd879d62efc0ddb6ddbca4b7293806 pm2_3.7
c436511946dc3928d961f0f9ada9a5cf pm2_3.7.bin
Oddly enough, they still appear to be the same file type. Can I really
flash a PM2 with either of these images and not hose the unit?
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____