>v3 can be used under w95, but it is still providing a 16 bit stack.
>(IMHO) I think it was for people who still wanted to run 16 bit
>internet apps that didn't like the w95 dialler.
Now I'm lost! Can I use v.3 under Win 3.11 (no win32s - that often takes a
few installs before one gets correct (I mean complete installs of windows
first and then win32s)).
> ] Actually I wonder why software
> ] companys specify Windows95 and 98 and just say DOS. Wouldn't it be more
> ] natural to list *all* the DOS versions (rather lengthy list) that work or
> ] only list one of each "OS"?
>
>You've lost me. Are you saying that companies are saying "needs W9x"
>but really need DOS. eg the soundblaster driver/initialiser that was
>discussed a few days ago???
They often state: "Works under DOS" and/or "requires Windows95, Windows 98,
Windows NT". What I mean is that they should list all DOS versions as well
if they list all Windows versions it works on. (It's not necisarely the
same program). Ex. Trumpet Newsreader for DOS works under "DOS" (big
suprise there <BG>) but WinSock v.4 works under "Windows 95 and Windows 98"
Why not list that as "Win9x" and DOS as "DOS 3.x+" (or whatever the minimum
is)?
This isn't very important anyway, so if you didn't get it, again (said in
Forest Gump style), then please ignore it (I can't explain it better than
this <G>).
>I mean, it says in the window that comes up with "you must add the
>trumpet directory to your path statement" or something.
Really? Never happened to me. If it's in the directory where TCPMAN.EXE is
then there will not be any problems. But other programs might like to reach
it as well.
>But what if you have more than one winsock file? [Well, I dont]. I
>try to keep as little sh-tuff in my windows directory as possible. I
>found more than 2MB of files in the system directory from a version
>of IE I thought I deleted a YEAR ago. And I've installed 3.11 from
>scratch since then. Wonder how that got there?
Doesn't ex. WinPlay require mwinsock.dll or winsock.dll to run?
> ] But I didn't have WinSock.Dll there to start with when I ran the
> ] installation program (it came along with Netscape 1.2 on a floppy from my
> ] first ISP).
>
>Isn't winsock.dll dialler-dependant? Or is this in the days when NS
>came with a dialler?
I've heard about this dialer before - can someone elaborate since I've
never used such a version (and imagine that mosaic was the coolest thing
when I tried the Net the first time).
I've got no idea if winsock.dll is dialer-depending - I know it works for
me the way it is and I'm happy (or perhaps I should say content since it's
still in Windows) with that.
>All a lot of ISPs give out is the phone number, username and
>password. eg I rang up (1800 number) tech support to get my DNS
>addresses, and he was hesitant to give it to me. But when I said
>"trumpet" he gave them to me as soon as he found them. (He was
>expecting me to run ShivaPPP which can get the 'dynamic' DNS)
Of the last three ISPs I've tried to get connection to for people only one
worked without problem. The other two didn't even give out a phone number.
Much less a user name or DNS (I don't count this time when I say
"installing" internet on Win9x takes an awfull alot of time - it would
easily increase since the tech support refuses to tell me everything at
once and I need to sit in line for up to 1 hour before they answer the next
question (and once again refusing to answer the next one before I've tried
with the information they've provided me)).
Hmm... Now I repeated myself from earlier.
On that matter wouldn't a (small) FAQ with the most asked question be good
to have around? This isn't the first time we've explained that a "winmodem"
is infact a "loosemodem". And we could even scream "RTFM!" to people asking
about it ;)
//Bernie
http://hem1.passagen.se/bernie/ DOS programs, Star Wars ...
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
