dgruest@cmx.npac.syr.edu (David Gruest) (03/01/89)
I seem to be having trouble getting binscii.
I give it the path name of the txt file i wish to convert back to prodos
then the path of a second 5 1/4 drive, It spins away and processes the
text file (i assume) and then stops. It doesn't write out the binary
file.
Can anyone tell me what's wrong?
I have an old //c (pre 3.5 upgrade) and external disk.
as well as a VERY old copy of Prodos.
Thanks in advance
David Ruest
dgruest@cmx.npac.syr.edudcw@athena.mit.edu (David C. Whitney) (03/08/89)
In article <1163@cmx.npac.syr.edu> dgruest@cmx.npac.syr.edu (David Gruest) writes: > >I seem to be having trouble getting binscii. >I give it the path name of the txt file i wish to convert back to prodos >then the path of a second 5 1/4 drive, It spins away and processes the >text file (i assume) and then stops. It doesn't write out the binary >file. > >Can anyone tell me what's wrong? I'll tell you: my User Interface sucks. It's hardly intuitive - but it was very easy to write. Here's the deal: When BinSCII asks for a pathname, it's asking for the complete or partial pathname of the file you wish to (un)convert. When it asks for a prefix, it wants to know where to dump the results of the processing. For example, if you had a BinSCII file sitting in your downloads directory and you want it to unpack to your testing directory, you'd type: Enter pathname -> /disk/downloads/newfile Enter prefix -> /disk/downloads/testing I am going to give v1.0.2 a good look over and then post it. It is essentially the same as v1.01, except that it prints out what it's up to (ie, unpacking n bytes into file <x>). I *do* intend to write a nice User Interface (similar in form to ShrinkIt's UI), but that takes time, and time is precious when you're a tooling MIT undergrad. Dave Whitney A junior in Computer Science at MIT dcw@athena.mit.edu ...!bloom-beacon!athena.mit.edu!dcw dcw@goldilocks.mit.edu I wrote Z-Link. Send me bug reports. I use a //GS. Send me Tech Info. "This is MIT. Collect and 3rd party calls will not be accepted at this number."
aash@ms.uky.edu (aash) (03/09/89)
In article <9663@bloom-beacon.MIT.EDU> dcw@athena.mit.edu (David C. Whitney) writes: >I'll tell you: my User Interface sucks. It's hardly intuitive - but it But, but but but... but the User Interface is the most FUN thing about programming! We all have our likes (and time demands i'm sure haha). Not criticizing aash -- aash aash@ms.uky.edu (archive at 128.163.128.6) {backbone site|rutgers|uunet}!ukma!aash "So aash, want some filet mignon?" "Nah, I was gonna have a hot dog."
ch1@cisunx.UUCP (Chris Helferty) (03/14/89)
In article <1163@cmx.npac.syr.edu> dgruest@cmx.npac.syr.edu (David Gruest) : > >I seem to be having trouble getting binscii. >I give it the path name of the txt file i wish to convert back to prodos >then the path of a second 5 1/4 drive, It spins away and processes the >text file (i assume) and then stops. It doesn't write out the binary >file. > I also have been having trouble getting Binscii to work with some of the posted files. I was never able to get the recent posting of a terminal emulator (ZLink?) to unpack and a couple of other things which I forget since I deleted them since they were apparently not going to unpack for me. I was only able to get Hyper C to unpack after concatenating the 8 files into 1 single file. This is only with *some* binscii`ed files (or should I say *most* ?). Some things have gone just fine such as the recent clock.system file and program selector. The symptoms are the same as those posted above. I give Binscii the pathname of the file to unpack. It checks the drive to make sure it's there then asks me for the destination. I give it the prefix for the second drive and then it checks for the existence of this drive. After finding it, it goes back to the first drive and begins to unpack. Except it never writes to the destination drive. Or any drive for that matter. It only reads from the packed file and that is all. Then it just stops as if everything went ok. I've done other things like giving a destination file name but then it just comes back with a file not found error (and I have to quit the program and restart it to clear this bug (a small bug I gather)). I have an older version of Prodos (version 1.1.1). Is this the problem? Any one else getting hassles? Whatever happened to executioner? Jon M. Pearsall
lwv@n8emr.UUCP (Larry W. Virden) (03/16/89)
I have used binscii to unpack a version of kermit that a friend sent me, Zlink, Shrinkit of a couple versions, and a number of other items, without any problems, on my IIgs. I am running in strictly prodos 8 text mode - no finders or anything like that (using ecp8 - thanks don!!!). I dont have any problems. Someone want to write an executioner <-> binscii converter <wink>? -- Larry W. Virden 674 Falls Place, Reynoldsburg, OH 43068 (614) 864-8817 75046,606 (CIS) ; LVirden (ALPE) ; osu-cis!n8emr!lwv (UUCP) osu-cis!n8emr!lwv@TUT.CIS.OHIO-STATE.EDU (INTERNET) The world's not inherited from our parents, but borrowed from our children.