Hello All
I've got a copy of the old Borland TASM v1.01 here, but can't get certain
stuff to work.
To be precise, I'm trying to use a "catstr", but no matter what I try it
does not seem to want to accept it. And yes, an Hexdump of the file
revealed it does know the word itself. :-)
So, I'm looking for a(n electronic copy of the) users-manual. If you have
one or know where to find one I would appriciate the information.
regards,
Rudy Wieser

Ian Gay <gay@sfuu.caschreef in berichtnieuws
Xns9810CCB33D88Bsfuidg@142.58.101.12

Hello Ian,

Don't have an electronic copy, but my paper copy says:

CATSTR Concatenates several strings to form a single string.
<snip>
Example LETTERS CATSTR <abc>,<def>

That is exactly what I tried. And every time I do it comes back with an
"illegal instruction" error.

Question : do you have a TASM v1.01 yourself, so you can see if it works for
you. If it does it must be a problem local to me. If not

Regards,
Rudy Wieser

"R.Wieser" <address@not.availablewrote in message
news:44ccfdf6$0$4526$e4fe514c@news.xs4all.nl
Hello All

I've got a copy of the old Borland TASM v1.01 here, but can't get
certain
stuff to work.

To be precise, I'm trying to use a "catstr", but no matter what I try it
does not seem to want to accept it. And yes, an Hexdump of the file
revealed it does know the word itself. :-)

So, I'm looking for a(n electronic copy of the) users-manual. If you have
one or know where to find one I would appriciate the information.

Nope.

Hey, did you ever find a solution for that network filesystem you were
writing? What was ituh, something with findfirst/findnext

Rod Pemberton

Rod Pemberton <do_not_have@bitfoad.cmmschreef in berichtnieuws
eanldc$299b$1@news.ndhu.edu.tw

Hello Rod,

<snip>

So, I'm looking for a(n electronic copy of the) users-manual. If you
have one or know where to find one I would appriciate the information.

Nope.

Too bad, I could really use one.

Hey, did you ever find a solution for that network filesystem you
were writing? What was ituh, something with findfirst/findnext

Correct. The answer is Yes, and No. Yes, I think I have found a method to
solve the not-closing of a communication-socket because a DS
find-first/next sequence does not know a find-close. The idea is to regard
any find-first or -next as a seperate action, using the index stored in the
DTA to signal to the other side which entry it needs to return.

, that could lead to problems when files get deleted or added to
that directory at the same time (files being skipped or appearing twice,
something I have not found a solution for)

And No, I have not implemented it yet : my intrest was pulled into another
direction.

Regards,
Rudy Wieser

"R.Wieser" <address@not.availablewrote in message
news:44cfc2c5$1$4526$e4fe514c@news.xs4all.nl
Rod Pemberton <do_not_have@bitfoad.cmmschreef in berichtnieuws
eanldc$299b$1@news.ndhu.edu.tw

Hello Rod,

<snip>

So, I'm looking for a(n electronic copy of the) users-manual. If you
have one or know where to find one I would appriciate the information.

Nope.

Too bad, I could really use one.

A couple Yahoo searches pulled up this:

They appear to be valid, but run them through your virus checker anyway

You might also want to try a P2P network"valuable" old software tends to
collect on them.

Hey, did you ever find a solution for that network filesystem you
were writing? What was ituh, something with findfirst/findnext

Correct. The answer is Yes, and No. Yes, I think I have found a method
to
solve the not-closing of a communication-socket because a DS
find-first/next sequence does not know a find-close. The idea is to
regard
any find-first or -next as a seperate action, using the index stored in
the
DTA to signal to the other side which entry it needs to return.

, that could lead to problems when files get deleted or added to
that directory at the same time (files being skipped or appearing twice,
something I have not found a solution for)

And No, I have not implemented it yet : my intrest was pulled into another
direction.

Yeah, I've got too many projects going on too!

I'm not sure if I posted these. First is some stuff on SDA. Second is
"network" ramdisk.

Ted Davis' original idea of calling findnext repeatedly when findfirst is
called and caching the results locally, may be the only solution

Rod Pemberton

Rod Pemberton <do_not_have@bitfoad.cmmschreef in berichtnieuws
eaosa4$b4g$1@news.ndhu.edu.tw

Hello Rod,

A couple Yahoo searches pulled up this:

ft/C_ASM/BRLAND

Thanks. Alas, a quick peek into that archive did not turn up any
user-manual documentation.

But its more complete than my own copy of Tasm v1.01 (which only contained
the minimal required files), so there is a good chance I still can learn a
thing-or-two from one of the included examples.

You might also want to try a P2P network"valuable" old software
tends to collect on them.

Hmmm That might be an idea.

I'm not sure if I posted these. First is some stuff on SDA. Second is
"network" ramdisk.

?hl=en

?hl=en

I've taken a peek at them, and have saved the pages for future reference.

I don't yet know if they will add something to my current knowledge though,
as I've got Ralf Brown's interrupt-list here, as well as the assembly-source
of Marcus Better's 'iHPFS for DS'.

Both where/are quite helpfull in providing details to general DS calls
(Ralf) and IFS handling (Marcus).

Ted Davis' original idea of calling findnext repeatedly when findfirst is
called and caching the results locally, may be the only solution

Would that not only move the problem to the local computer : when to release
the cached results ?

Thanks for your input and the links.

Regards,
Rudy Wieser

Ian Gay <gay@sfuu.caschreef in berichtnieuws
Xns9812D23FCB3B0sfuidg@142.58.101.12

Hello Ian,

Question : do you have a TASM v1.01 yourself, so you can
see if it works for you. If it does it must be a problem local
to me. If not

I tried it. In default assembler mode it is not accepted. In
MASM51 or IDEAL mode it is.

Ahhh That explains it. I never would have thought of that though, as
I normally only use the standard Tasm mode. Maybe I should take a peek at
those two modi, even if it is only to see that "catstr" working :-)

Thanks for your help,

Regards,
Rudy Wieser