TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Rod Speed
from: Paul Edwards
date: 1996-09-10 22:28:44
subject: dickhead alert

PE> "Everything needed" includes batch file with
PE> qwk2pkt call, plus the area list table.

RS> Sorry about my lack of mind reading skills. I've kept the same name.

PE> What the fuck have you sent me, Rod?

RS> What you appeared to want.

PE> For starters, I expected a one-line batch file,

RS> Odd, could have SWORN that that line of yours right at the top
RS> says nothing remotely like that. 

No, you're meant to figure that out for yourself.

RS> I dont read minds you know. You
RS> appeared to be asking for the BAT file what was actually used.

The idea is that YOU have to demonstrate that it is a bug in QWK2PKT. Once
you've done that, you send me the stuff required so that I can see the bug.
 Then I can debug it.

I am not interested in bugs in your batch file, or forgetting to put in
parameters etc etc.

At this stage I don't even KNOW that it's a bug in QWK2PKT.  I said
previously that if you could demonstrate a bug in QWK2PKT, I would look
into it.

PE> not one that I had to debug and guess before I could use it,

RS> Even you should have been able to see the QWK2PKT line
RS> and cut that out and use if if you wanted a one liner.

I had to guess what %1 was used for, then I had to stuff around finding out
what input it was expecting.  YOU should have cut that one line out.

PE> and then debug and guess why it couldn't find tenmin.msg
PE> when it turned out it was zipped in .rep instead.

RS> Welp, that cant be done with a one liner, soorree.

YOU SEND ME THE UNZIPPED FILE!!!  I am not interested in a bug in your
unzip program, I'm not interested in bugs in your batch file. I only said I
would debug QWK2PKT.

PE> Secondly, once I'd wasted my time doing that, it turned
PE> out that there were only two messages in the bad.zip,
PE> and they were being converted successfully anyway, ie you
PE> have NOT SENT ME WHAT I NEED TO REPRODUCE THE PROBLEM.

RS> Or that that msg produces a dud PKT in SOME circumstances as yet
RS> unresolved Paul. That is not exactly unheard of in computing and
RS> is also a good reason why sending you a one liner which isnt what
RS> is actually used to produce the PKT isnt exactly a terrific idea.

Rod, it is a terrific idea.  There is ABSOLUTELY NO DISADVANTAGE in having
a one-liner.  Because if you can't reproduce the problem yourself in a
one-liner, I'm not interested.

PE> It would have been wise to include the executable you are using as well.

RS> I dont read minds. Its easy to see that that is desirable
RS> AFTER we see that you get a different result on your system
RS> than mine, to check to see if the EXE is actually identical.

I said "everything required to reproduce the bug".  You sent me a
batch file that references directories I don't have, etc etc.

RS> I've added it to that ZIP file and uploaded it again with the same name.

You added the wrong executable.

Try again.  A one-liner, get rid of any crap, I'm not interested in the
zip-compressed file etc.  Just the minimal number of files used by QWK2PKT.

PE> BTW, I noticed in your batch file that you are doing
PE> a rename at the end. That's not a good idea, you should
PE> just blanketly convert all 00000000 to 00000002.

RS> Pity you havent actually shown why thats the only way to go.

It was only a comment, I don't actually care so long as I get the 00000002
arriving here, for management and integrity.  BFN.  Paul. 
@EOT:

---
* Origin: X (3:711/934.9)

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.