On Oct 19, 2025 at 2:46:35 PM MST, "Gremlin" wrote <XnsB37DB4D4D4165HT1@cF04o3ON7k2lx05.lLC.9r5>:Did you say something snit?
"Apd" <not@all.invalid>
news:10d32bu$2k6s8$1@apd.eternal-september.org Sun, 19 Oct 2025
16:07:11 GMT in alt.computer.workshop, wrote:
"Gremlin" wrote:
https://dosbox-x.com/
I wasn't aware of it so thanks for mentioning. It's more up to date
than Dosbox and looks better maintained. I'm now mostly on 64-bit
systems so I installed Win 3.11 under it for a couple of oldies I
sometimes like to run.
No problem. I found out about it while searching for an easy way to
show the command line and what AZ would do if you provided invalid
run parameters on it. It was in response to Snit claiming he made it
very easy to use - As if it wasn't already piss simple to use as I
wrote and released it years ago.
If you think
On Oct 19, 2025 at 6:33:57 PM MST, "Gremlin" wrote <XnsB37DDB60EE858HT1@cF04o3ON7k2lx05.lLC.9r5>:
"Apd" <not@all.invalid>
news:10d3qfm$2rb8n$1@apd.eternal-september.org Sun, 19 Oct 2025
22:58:11 GMT in alt.computer.workshop, wrote:
"Gremlin" wrote:
Not only does Snit still not seem to understand why I wrote AZ in
the first place, he also doesn't understand why his 'easier' method
isn't as good as he thinks. I haven't found a reliable source that
says the extended ascii character set can just be copy pasted as is
into an empty file from the clipboard on MacOS. From what I've
read, it won't do it. Which defeats the purpose of using AZ in the
first place. I accept that I could be wrong, MacOS isn't my daily
driver and I don't have any machines here running it to do any
testing with.
Nor do I any more.
:) For text and only text it's fine. I still think the command line
:as was
originally intended is the better way to go. But, for the purposes of
moving binary files thru systems which didn't allow it for various
reasons - Snits method isn't suitable. If you meant something else,
Please clarify?
My method of decoding AZ Code when it is used as a cipher is suitable.
You simply are not clever enough to understand what you are seeing:
https://drive.google.com/file/d/1dsmEE2-xgiYJEUMfn4fjuPqp0zUe7ltw/view
AZ Code is not as complex as you try to make it seem:
https://drive.google.com/file/d/14_W7lBUriKUprzudChOGaEDpJ6k9K45K/view
It may try to interpret binary as utf-8 text.
That's what I've seen repeatedly in my efforts to narrow down a
simple yes or no concerning it's support for the entire ASCII
character set.
Things like
On Oct 19, 2025 at 9:25:00 PM MST, "Gremlin" wrote <XnsB37E43D03B65HT1@cF04o3ON7k2lx05.lLC.9r5>:
"Apd" <not@all.invalid>
news:10d3qfm$2rb8n$1@apd.eternal-september.org Sun, 19 Oct 2025
22:58:11 GMT in alt.computer.workshop, wrote:
Nor do I any more. It may try to interpret binary as utf-8 text.
Scratch the clarification question. I understand what you meant. I
wasn't giving your post the attention I should have been at the time.
That's on me. I haven't found anything definitive that indicates you
could use Snits method with binary files. Everything I've read about
it so far indicates it won't work. He probably didn't build a table
suitable to cover the entire ASCII table anyway so it's a moot point.
For the way
Only those open
On some things, clearly. But sorry for my error,
On Oct 20, 2025 at 5:56:33 AM MST, ""Apd"" wrote <10d5biu$37ahd$1@apd.eternal-september.org>:
"Gremlin" wrote:
"Apd" wrote:
It may try to interpret binary as utf-8 text.
That's what I've seen repeatedly in my efforts to narrow down a
simple yes or no concerning it's support for the entire ASCII
character set.
Originally, Snit made a lookup table with a spreadsheet which didn't
cover all byte values. He later used a direct calculation method (as
I did) in Applescript which did.
Correct
Right.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,073 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 213:08:29 |
| Calls: | 13,782 |
| Files: | 186,987 |
| D/L today: |
38 files (4,791K bytes) |
| Messages: | 2,434,588 |