| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 134.1 | | JAMIN::WASSER | John A. Wasser | Fri Feb 21 1997 11:42 | 5 |
| > Is there any pointer for the documentation of PATHWORKS 32 on Easynet ?
I think that the only documentation is Help files. They are
hyperlinked and indexed so they would not be easy to follow
in hard-copy form even if you could get them that way.
|
| 134.2 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Fri Feb 21 1997 13:28 | 1 |
| there is supposed to be a User's Guide, I don't have a pointer though.
|
| 134.3 | | PEACHS::GHEFF | Got a head with wings | Fri Feb 21 1997 13:53 | 8 |
| The MCS Learning Utility has a pointer to a page, but the page doesn't
yet have a pointer to a PS file.
http://www-mcslu.das.dec.com/mcsl_abs/aa-r36va-te.html
http://www-mcslu.alf.dec.com/mcsl_abs/aa-r36va-te.html
http://www-mcslu.cxo.dec.com/mcsl_abs/aa-r36va-te.html
#Gary
|
| 134.4 | prefer hardcopy to online PW32 API docs (personally) | DECALP::KLAVINS | Ed Klavins, RTR Engineering | Sun May 25 1997 09:15 | 19 |
| >
> I think that the only documentation is Help files. They are
> hyperlinked and indexed so they would not be easy to follow
> in hard-copy form even if you could get them that way.
That's a shame. We have code using Pathworks for NT V4 (winsock 1.1 w/
decnet) and Pathworks V1 for W95 (non-winsock). I want to investigate
what we need to do to bring these to a common code base again with
PW32 and winsock 2. I personally find it much more productive to take
the hardcopy API manual home, sit back, and peruse the manual making
notes, flipping back/forth thru the pages etc. I had a quick look at
the online help for PW32 API manual, and it's a real pain to use it for
what I want to do...
Is there really no .PS around somewhere of the API?
(also, couldn't find the MCS learning utility files referenced in .-1)
ed
|
| 134.5 | Really, no docs | JAMIN::CURLESS | The Dream Police. | Tue May 27 1997 07:43 | 16 |
| I like to have hardcopy as well, however the world seems to be
convinced software engineers don't need it.
I don't think we have a PS file, more like multiple files that need
to be combined, IF there is anything. The review copy I had was just a
print out of the help pages (not a document in my opinion).
As for the real issue... Winsock 1.1 is fully supported in a Winsock
2.0 environment, and has the added value of not forcing you to make
code changes. If the DECnet service provider, and Winsock 2.0 is added
to Windows 95, the code you have that works on PATHWORKS 32 for NT
v4.0, will work on Windows 95 (unless it requires NT specific
functions, outside of the Winsock space).
Jeff
|