| Electronic Design Laboratory |
 |
17 Caledonia Place
Bristol
BS8 4DJ
UK |
Tel: (+44) 117 974 1918
Fax: (+44) 8700 558558
dcc@tecno.demon.co.uk |
Home
...
The Windows95 Direct Cable Connect Problem Page
Microsoft doesn't offer any advice on the immensely useful Direct Cable Connection
utility so here is a web page full of email and other stuff that may help people
to get their Direct Cable Connection working. It's made up from the contributions
of many frustrated DCC users. If you discover something useful PLEASE send an
email so I can update the page!
Last updated: 23 February 2004
Parallel Lead Wiring Diagram
This is nice and quick. They can be purchased easily. Just ask for a Laplink cable. If
you want to make one here are the connections:
To use the Direct Cable Connection program you need a Serial Null Modem
cable or a Bi-directional Parallel Cable to connect the two PC's together. It is
worth the effort to either purchase or build the Bi-directional Parallel cable and there
are only a few more wires to connect above the serial cable.
File transfers using the Bi-directional cable are from eight to ten times faster than
the Serial Null Modem cable.
With the Host PC connected to a Network you may be able to access resources on the LAN
without a network card in the client PC. You can even use it to install CD-ROM software
onto a Laptop that does not have a CD-ROM drive, providing the Host PC has a CD-ROM drive
or one is available on the LAN.
Bi-directional parallel cable: Two 25 way D-type male connectors, and a cable
containing at least eleven conductors. Connect pins as follows:
Signal
name |
Computer #1
25 way D connector |
Computer #2
25 way D connector |
Signal
name |
| D0 |
2 |
15 |
? |
| ? |
15 |
2 |
D0 |
| D1 |
3 |
13 |
? |
| ? |
13 |
3 |
D1 |
| D2 |
4 |
12 |
? |
| ? |
12 |
4 |
D2 |
| D3 |
5 |
10 |
CK |
| ACK |
10 |
5 |
D3 |
| D4 |
6 |
11 |
BUSY |
| BUSY |
11 |
6 |
D4 |
| GROUND |
25 |
25 |
GROUND |
ECP Parallel Lead Wiring Diagram - Untested, For the experts only!
Oliver Knorr said::
Microsoft mentions the different types of parallel cables in the Resource Kit and
Knowledge base. For example, what MS calls "UCM = universal cable module" is not
simple cable, but includes an electronic circuit in one of the connectors. Apparently is
is available only from "Parallel Technologies" (http://www.lpt.com/lpt/), which
do not call it UCM cable, but "direct parallel universal cable", to make things
more confusing. In Germany, this cable is available from "Primax"
Even more complicated is the "ECP cable". It seems to be available form
"Warp Nine Engineering" in the US (http://www.fapo.com), but absolutely
impossible to get in Germany. Another thing completely impossible to get is the pinout of
this cable, at least without buying the whole original IEEE 1284 document.
This is the latest specification I have on such a cable
ECP Compliance Test Loopback Cable Assembly
Start using a FP-AMAM-10 (IEEE1284, DB25 Male to DB25 Male)
Mark one connector "H" and one connector "P"
| Name |
Pin |
Dir |
Name |
Pin |
| |
|
|
|
|
| nStrobe |
1 |
> |
nAck |
10 |
| Data |
2..9 |
<> |
Data |
2..9 |
| nAck |
10 |
< |
nStrobe |
1 |
| Busy |
11 |
< |
nAutoFwd |
14 |
| PError |
12 |
< |
nInit |
16 |
| Select |
13 |
< |
Select, nSelectIn |
13,17 |
| nFault |
15 |
< |
nSelectIn |
17 |
| nAutoFwd |
14 |
> |
Busy |
11 |
| nInit |
16 |
> |
PError |
12 |
| nSelectIn |
17 |
> |
nFault |
15 |
| GND |
18..25 |
|
GND |
18..25 |
There is also a postscript formatted file (ecp-ps.zip)
from Microsoft which details the ECP port specification but it only refers to a test cable
of the following wiring plan. I only have this file in postscript, sorry. Here's an
extract from it on the subject of wiring:
Hardware Test Setup
The test is set up on a single ISA PC. Two ECP cards are placed in a PC at different LPT
port
addresses (0x278, 0x378, 0x3bc). The cards must use interrupt and DMA channels that do no
conflict with any devices existing on the system.
After the cards are installed, they are connected together with a cable in such a way that
the
ECP handshake lines are swapped; this allows loop back testing of ECP functions.
Port-to-Port Test Cable Connections
The cable Microsoft describe is as the table above
Serial Lead Wiring Diagram
This is very slow so generally not worth bothering despite its fewer wiring
connections. The DCC serial null-modem cable offers limited speed (<10 kbytes/sec).
Parallel cables are preferable to serial cables because they are 4 - 40 times faster.
Serial Null Modem cable: Two 25 or 9 way D-type connectors, and cable with at least 7
conductors. Connect pins as below:
Signal
name |
Computer #1
9 way D connector |
Computer #1
25 way D connector |
Computer #2
25 way D connector |
Computer #2
9 way D connector |
Signal
name |
| TD |
3 |
2 |
3 |
2 |
RD |
| RD |
2 |
3 |
2 |
3 |
TD |
| RTS |
7 |
4 |
5 |
8 |
CTS |
| CTS |
8 |
5 |
4 |
7 |
RTS |
| DSR |
6 |
6 |
20 |
4 |
DTR |
| DTR |
4 |
20 |
6 |
6 |
DSR |
| GROUND |
5 |
7 |
7 |
5 |
GROUND |
NOTE: Some motherboard need Carrier Detect signal enabled else a message "cable
not connected" appears in the connection window. In this case the cable works only if
the pin 6 and 8 (25 pin connector) and the pin 6 and 1 (9 pin connector) get wired
together.
What is 'Peer Networking'
Brian Pierce said::
"Peer networking" means that you don't need a file server to share resources
(like files and printers) on a network. Machine A can make some of its resources available
to Machine B, and vice versa. (So Machine A can print to Machine B's printer, while
Machine B is looking at files on Machine A.) Real file servers are highly optimised for
enabling large numbers of clients to access and share its resources. They actually perform
poorly as user workstations due to these optimisations. Peer networking allows a user
workstation to perform kind of like a file server, but without the industrial strength
performance of a real file server.
In DCC, one machine is designated as the "host" and the otheras
"client". The host machine makes resources available (i.e., shares them), and
the client uses the resources.
You might call this 1-way peer networking - but this is not 2-way peer networking.
In consequence: With DCC, the guest will be able to explore the files of the host
but not vice versa.However ...
Tricking DCC into doing 2 way peer networking
Gene H. Chan said::
I read a posting in a newsgroup where someone said one could get the equivalent of a
peer-to-peer network with DCC. You start up DCC with one PC as the host and the other as
guest, as usual. You then shut down DCC. Now, start up DCC with the roles reversed, i.e.,
configured with what was the host in the first instance now acting as the guest, and
vice-versa. Apparently, after doing this, each node can access the other node's shared
files/folders.
Tim Craig said::
I explored this and found that the [host-guest]/[guest-host] swap was not actually
required. Connect the two computers together as usual but on the host machine create a
shortcut to
' \\Remote_machine\shared_folder '
The host will probably object and ask if you want to use 'Dial-up networking', Ignore
that, close the dialog box and voila...the explorer window will pop-up displaying the
guest machine's shared folders.
This works over the dial-up connection too!
Computers must have different names
Cliff_Spitser said::
My problem was that the guest could not find the host after the connection was made.
The advice under "System Seems to Connect but Can't find the Host Computer" said
to remove IPX/SPX. When I did that, I got the message "Parallel cable
Disconnected" My DCC started working after I made the computer names different.
(Previously, both computers had the same name)
System Seems to Connect but Can't find the Host Computer
Tim Craig said::
I used to get this when I had IPX/SPX installed under Network Properties. Add the
protocol 'NetBEUI' and remove the IPX/SPX protocol. I also made NetBEUI the default
protocol on my host machine which also had TCP/IP installed.
LM Announce
This setting will announce the presence of this machine to the Browse Master so it
becomes listed in the Network Neighbourhood.
Tim Craig said::
If enabled this also has the quite undesirable effect of causing the PC to take forever
to shutdown. It will, eventually, but it gives a very good impression of a system hang-up.
I have managed to make Network Neighbourhood work even with this feature disabled anyway.
Leave it set to 'No'
IPX/SPX
Well the Windows95 dialog box which is under Network Neighbourhood 'properties'
displays the following text if the IPX/SPX item is highlighted.
The IPX/SPX compatible protocol is a protocol NetWare
and Windows NT servers, and Windows 95 computers
use to communicate.
Despite this, don't use it on Windows95. Remove it from the system. Using this protocol
for DCC is the most common cause of the guest machine being ' unable to find shared
folders '
Having having found this ourselves Microsoft have a knowledge base item
on the subject which differs. See: http://support.microsoft.com/support/kb/articles/Q127/1/36.asp
NetBEUI
The Windows95 dialog box which is under Network Neighbourhood 'properties' displays the
following text if the NetBEUI item is highlighted.
NetBEUI is a protocol you can use to connect to Windows
NT, Windows for Workgroups, or LAN Manager servers
Note the absence of any mention of Windows 95. Despite this, have this protocol
enabled.
Browse Master
This setting determines which computer on the network carries out the job of finding
out who is on the network. One computer per workgroup should have this set to 'Enabled'.
In order to see the host computer's resourse, you have to set the "Browse
Master"(in the property sheet for File and printer sharing for Microsoft networks) to
"Enabled" (instead of the default "Automatic") on host computer. But
don't do this on the guest computer.
Network Neighbourhood Icon - Unable to Browse the Network
If the 'Browse Master' is set to 'enabled' on both machines this should work. MS
disables this function by default for DCC, but enables it by default for other networking.
i.e. If it is set to 'auto' it will be disabled
It seems to take a short while, 15s or so, after the DCC connection has been
established before it finds the remote machine however.
What is NetBIOS
Well this is what Richard Ashton had to say on the subject:
In article tfl@psp.co.uk "Thomas Lee" writes:
} X-No-Archive: Yes
} In article <847134321snz129.os2.7@horizon.co.uk>, Richard Ashton
} writes
} >NetBIOS and NetBUEI ar two halves of the same protocol like IPX/SPX ish
}
} Actually, {R}, this is not correct, at least on Win95.
}
} NetBios is at a level above NetBeui. In all the Windows Networking,
} NetBios can be bound to any transport protocol (i.e. IPX, TCP/IP or
} NetBeui). Applications call netbios which, in turn, can utilise any of
} the bound protocols.
Actually {R} is correct he just didn't put them the right way round
NetBIOS is a program application interface. It interfaces in OS/2 and
NT and Win95 to NetBEIU which talks to the NDIS layer.
OS/2 has a TCPBUEI stack that is not present in BillyShit that allows
routeable NetBios applications.
NetBIOS over TCP/IP as implemented by Microsoft is RFC 1000/1001, This
is an encapsulation not a BUEI type interface
NetBIOS over IPX is a joke.
{R}
Toby Groves said this:
Just a note on NetBIOS. Most protocols, like TCP/IP, are really two things:
(1) they define a set of "commands" that programmers use to establish and
control network communications; and ...
(2) they define the underlying protocol, which actually does the nitty gritty sending and
receiving of network messages.
NetBIOS ONLY does (1). NetBIOS, however, is almost ALWAYS used with NETBEUI, which does
(2).
Many people use the term NetBIOS to refer to both real NetBIOS and NETBEUI. (When you
install the "NetBIOS" protocol in Win95, you're really installing
NetBIOS/NETBEUI).
However, it is possible to use NetBIOS with part (2) of some other protocol (like
IPX/SPX). (This will not be compatible with another machine running NetBIOS over NETBEUI!)
One of the configuration options for IPX/SPX is to enable NetBIOS over IPX/SPX. DON'T
DO THIS (unless you have a VERY good reason)! I believe that the only reason to use
IPX/SPX for anything is if you are interfacing to a Novell network (and even then, I
wouldn't enable NetBIOS over IPX/SPX). Like I said, I don't really understand why you even
have to install it.
DCC Command Line Options
DCC definitely responds to some command line options. I tried '/doggy' and it caused it
to avoid the initial prompt dialog. So did '/a', '/b', '/c' but I have not tried any more.
This is only true for the host computer. On the guest computer it appears to stop DCC
from loading.
Some experimentation required
Parallel Ports : SPP / EPP /ECP
All these ports will work with Direct Cable Connection. It is selected from the BIOS on
computer start-up. I have it on good authority that the link between 2 EPP or ECP ports
can be nearly as fast as 2 NIC ethernet cards. Generally select ECP
| ACRONYM |
SPEED |
DESCRIPTION |
| SPP |
OK |
Standard Parallel Port. Include unidirectional (4BIT) ports and
bidirectional (8BIT) ports. These ports are generally found on PCs built prior to 1995 |
| EPP |
FAST |
Enhanced Parallel Port. Capable of high-speed operation and are
most often found on laptop systems with Intel SL or SL-compatible chipsets. |
| ECP |
FASTEST |
Extended Capabilities Port. Capable of high-speed operation and
are most commonly found on PCs built after 1994 which use I/O chipsets from SMC, National,
and so forth. |
How can I determine which type of parallel ports are in my system?
See what is available for selection in the BIOS setup. Or download the Parallel Port
Information System (Parallel.Exe) and run it on your system in DOS mode.
Download the program: parallel.exe now.
Technical background
4bit ports
The port can do 8bit byte output and 4bit nibble input. These ports are often called
"unidirectional", and are most commonly found on desktop bus cards (also called
IO expansion cards, serial/parallel cards, or even 2S+P cards) and older laptops. This is
still the most common type of port, especially on desktop systems. 4bit ports are capable
of effective transfer rates of about 40-60 KBytes/sec (KBPS) in typical devices and can be
pushed upwards of 140 KBytes/sec with certain design tricks.
8bit ports
These ports can do both 8bit input and output. These ports are sometimes called
"bidirectional ports", but that term is often misused by some vendors to refer
to 4bit ports as well. Most newer laptops have 8bit capability although it may need to be
enabled with the laptop's vendor-specific CMOS setup function. This is discussed below. A
relatively smaller percentage of LPT bus cards have 8bit capability which sometimes must
be enabled with a hardware jumper on the board itself. True 8bit ports are preferable to
4bit ports because they are considerably faster when used with external devices that take
advantage of the 8BIT capability. 8bit ports are capable of speeds ranging from 80-300
Kbytes/second, again depending on the speed of the attached device, the quality of the
driver software, and on the port's electrical characteristics.
EPP ports
Can do both 8bit input and output at ISA bus speeds. These ports are as fast as 8bit
bus cards and can achieve transfer rates of upwards of 1 Mbyte/sec.
ECP ports
Can do both 8bit input and output at bus speeds. The specification for this port type
was jointly developed by Microsoft and Hewlett-Packard. ECP ports are distinguished by
having DMA capability, on-board FIFOs at least 16 bytes deep, some hardware data
compression capability, and are generally more featured than other ports. These ports are
as fast as 8bit bus cards and can achieve transfer rates upwards of 1 Mbyte/sec and faster
on PCs whose buses will support it. The design is capable of faster transfer rates in the
future.
The Dial-Up Server from the MS-Plus pack
Tim Craig writes:
Obviously a modem is required for this great little utility that will allow you to
carry out DCC style file transfers and browse the files on the remote machine as if it
were on a network. You need the Win95 Plus-Pack to get it though.
When it's loaded there will be a new item called 'Dial-up server' under the
'Connections' menu item of 'Dial-up Networking'. Go to that item and check the 'Allow
Caller Access' box
Tip: If you limit the shared folders to only those that you wish to make public
to the people who will be dialling into your machine then you can access all of the drives
irrespective of the shared status by enabling the 'remote administration' feature. This
uses a different password. To set it up
Control panel
Passwords
Remote Administration = checked
However you can have the dial-up server without the Plus-Pack! Recent observations from
Chris nellesc@sprint.ca regarding the use of the
use of the Plus-Pack to gain access to the dial-in server are described in the following
Microsoft Word document: DCCSVR
Getting DCC to work in conjunction with TCP/IP
If the computer is already running TCP/IP then there can be some conflicts with Direct
Cable Connection. Horror stories please!
Preparing Your Computer For DCC
The important thing is to make sure your printer port is configured for DCC
communication. Both computer must have same printer port configuration.
In your BIOS setup, check the section regarding ports setup, usually in the chipset
setup for newer motherboards. There will be a section that configure the printer port.
There is two printer sections: one is IRQ and the other is type of communication. In the
type, make sure it is in the ECP mode or EPP + ECP mode. Save and exit.
Getting DCC running
If DCC has been properly installed this is what you should see under the 'properties'
of Network Neighbourhood or on selecting the 'Network' icon under control panel. TCP/IP is
not required, IPX/SPX will probably be present - remove it.
Network Neighbourhood must be on the desktop. If it isn't then you can
re-install it from your Win95 disc or if you have TWEAK-UI it can be done from there.
Go through the items one by one and configure as set out below, Many items will already
be set this way by default.
Network Neighbourhood
Properties
NetBEUI installed
Properties
Bindings
Client for Microsoft Networks = Checked
File and Printer Sharing = Checked
Advanced Maximum Sessions =10
NCBS = 12
Set this protocol to be default = checked
IPX/SPX not installed
TCP/IP (if installed)
Properties
Bindings
Client for Microsoft Networks = Checked
File and Printer Sharing = Unchecked
Dial-up adapter installed
Driver type
Enhanced mode
Bindings
NetBEUI = checked
TCP/IP = checked
Advanced
Record a log file = No
Use IPX header compression = yes
Client for Microsoft Networks installed
Properties
General
Log-on and Restore Network Connections = checked
File & Printer Sharing
Properties
Advanced
Browse Master 'enabled'
LM Announce 'No'
Log-on set to 'Windows'
File & Printer Sharing (Button)
In want to give others access to my files = checked
I want to be able to allow others to print to my printer = yes
Now connect a cable between the ports you have defined on the two machines.
If you get no indication of any sort of link being made at all then consider the cable
is at fault. A good test at this point is to run the Intersvr / Interlnk program
from a prevous DOS installation. This is ideal as it needs no setup, uses a fixed protocol
and automatically searches through all the ports to find the link. If you sill can't
establish communications with this application then your cable is most likely to be at
fault.
To set up Interlnk/Intersvr:
Add the line 'device=c:\dos\interlnk.exe' to 'config.sys' on one machine.
(You should create a 'config.sys' file if it does not exist)
Reboot this machine.
Run the program 'INTERSVR.EXE' on the other machine
Once you have ascertained that the cable is good/bad remove the interlnk.exe
from the respective computer config.sys file as it will cause interference with Win95
operation making it run in compatibility mode.
Really Basic Stuff
How do I install DCC
CONTROL PANEL
ADD REMOVE PROGRAMS (icon)
WINDOWS SETUP (tab)
COMMUNICATION (item on list)
DETAILS (button)
DIRECT CABLE CONNECTION (item) <<< Check this item
Slow Shutdown after installing DCC
Tim Craig said::
You need to disable 'LM Announce' from the:
Network Neighbourhood:
Properties
File & printer sharing
Properties
Advanced
LM announce = No
My understanding of this is that Shutdown, with LM announce enabled, causes Win95 to
try and send a message to the network that it is about to depart. If the network is not
there anymore (because DCC has since been terminated) then it waits a while before giving
up on any response arriving.
Sharing a modem via DCC
To share a modem over a DCC link. First and formost, download the Dial Up Networking
1.2b upgrade and associates Winsock upgrade from Microsoft. Try
http://www.microsoft.com/communications/PPTPdownNow.htm to get the stuff. Install it an
reboot (on the host computer only.)
You now have 2 dial up adapters, #1 will be for internet, in my case my cable modem,
and #2 for DCC. You must always connect to the net first to force this order!!!!
Remove all network protocols except TCP/IP (you can have other installed, but to make
it easy the first time remove them). Be sure Network bindings are TCP/IP bound to both
Dial Up Adapters on the host, and on the only dialup on the guest. You can install the DUA
upgrades on both if you like. Also, enable file and printer sharing on both system, and
enable Browse Master 'enabled' and LM Announce OFF for BOTH systems, select Windows Logon,
and be sure Client for MS networks is installed. Click on TCP/IP settings for Dial Up #2.
Select IP ADDRESS, and enter Specify an Address. Enter 90.0.0.1 for the host, and 90.0.0.2
on the guest machine (we're doing both at once here.) Also, enter 255.255.255.0 as subnet
mask on BOTH systems. Select the tab DNS configuation for the GUEST system. Click ENABLE
DNS, and enter 90.0.0.1 and hit ADD. You are done here with both systems.
Start up your internet connection, then load DCC on both systems. They should connect.
if not, be sure all bindings, etc. are correct.
Load your favorite proxy software, I use WinProxy and config to their instructions.
Configure all client software on the guest machine to use a proxy server, 90.0.0.1 for
internet access and you are all set!
---------------------------------------------------------------
This is mainly for those who wish to access a modem attached to the internet on the
host machine from a DCC linked machine.
crockett@txcc.net replied to this question::
| I have two computers, one connected to the Internet via a network
| card, the other connected to the first computer via a parallel
| cable. My question is: If it is possible, how do I get the second
| computer connected to the Internet, using the first computer as a
| host? I have installed NetBEUI, IPX/SPX, TCP/IP on both
| computers, |and shared resources appear already on both.
|
| Responses via e-mail would be appreciated.
TIA
You have to get a router software such as WINGATE. get it from www.windows95.com
I would welcome some input on this. Maybe somebody could explain how
it's configured. dcc@tecno.demon.co.uk
From: Craig Southeren Well, let me give you the configuration I am using here: Laptop W95
Desktop Machine 10.0.6.2 <===dcc===> 10.0.6.1 NT Server 10.0.4.102 <=== lan="=="> 10.0.4.100 <=== internet via dialup my laptop is connected to my normal work machine via a dcc connection. during the day, i just leave it connected, grabbing mail and stuff, via the internet connection at work. note that neither my dekstop machine or the laptop have "public" ip addresses. i have a company that sells a product called firedoor, which is the cheapest and simplest proxy server available. you can use it free of charge for the above configuration, as there is only one user. i am actually running two copies of firedoor in the above scenario one on the server for all lan users, and another my desktop machine just for me. it works just great! i can surf, check email, read news, ftp everything>from my laptop just
fine. You can get more info from our web site, or just email me for more info. Web:
http://www.equival.com.au/~equival
Connection a Windows 95 machine to a Windows for Workgroups machine
Jay Lowe replied to this question::
> Is there a way to make DCC work with Windows for Workgroups 3.11 ?
Not immediately ... if 3.11 RAS is compatible with Win95 RAS, then we can
probably bring it up by porting the DirectParallel driver to 3.11 ... else we
have to switch to using NDIS on both ends (which would buy us some useful speed
anyway).
Tim Craig said::
DOS 6 comes with a program called Interlink to provide communications over the parallel
or serial port. It comprises two programs: INTERLNK & INTERSVR. It forms a simple but
effective utility to transfer files between a pair of computers. To use it add the line:
DEVICE=C:\DOS\INTERLNK.EXE
to the CONFIG.SYS file of the Win3.1 or Windows for Workgroups computer. On the second
computer drop to dos and execute the program:
INTERSVR.EXE
The Win3.1 computer will now be able to access additional 'drives' mapped from the
second machine.
Warning: The two programs can be reversed but if you do this don't leave the
INTERLNK line into the CONFIG.SYS file of the Win95 machine as it will cause it to run in
'compatibility' mode.
Email repository
There is plenty of useful case history here. If you are having problems you will see
that you are not alone.
----------------------------------------------------------------------------------------------------------------
From: Richard Kaye
I have literally spent months (on and off) trying to get DCC to
work between my laptop (Windows ME) and an old desktop
(Win95). Your pages were easily obtained, but not much help.
I had all but given up, but when I started trying to
set up a similar connection in a different OS I realised that
the problem was that PnP wasn't working properly.
It's sort of obvious, but I didn't ever see it written anywhere,
that the port being used MUST have an IRQ. I was using LPT2
and windows gave it first no IRQ at all then it gave it IRQ3.
PnP had previously bagged IRQ5 for my sound card.
I needed to change the BIOS settings to un-bag it
Eventually I was able to manually set my printer port to use
IRQ5. Windows then unhelpfully told me I'd have to change the
jumper settings (I ignored this advice) and on restarting it worked.
----------------------------------------------------------------------------------------------------------------
From: John Wong
I certainly didn't expect to get multi-protocol support. I now play TCP/IP and IPX/SPX games as well as share folders over DCC.
So why are people using Null Modem Drivers (MDMCBX.INF) with Dial-Up Network connections with dummy phone numbers and DUN Server instead of just DCC? Not only is it simpler to set up, but you can run any protocol you want at nearly Ethernet speed over a parallel cable!
I may have found how to increase the speed of a Serial DCC link. I was getting speeds of 2500 bytes/sec when I set up the link last week. I had tried setting the COM port settings in Device Manager to 115200, but this had no effect.
Today I got an email suggesting the Control Panel->System->Device manager->Modem settings. It was there under 'Serial cable on COM1'
and it was set to 19200 bps! I haven't tried it yet but I'm going to set it to 115200 as soon as I can. (I must have been looking in System->Modem before; that only has entries for real modems).
--------------------------------------------------------------------
From: Peter Lawson
I advise that I have today in practice confirmed that different versions of
directcc.exe fail to communicate, specifically that a file dated 11.7.95 time
09:50 on the guest could not work with one dated 24.8.96 time 11.11 on the host.
I copied the latter onto a diskette, renamed the former, substituted the file
off the diskette and all worked fine. Before doing this the computers appeared
to connect, tried to verify password and then the guest showed the message "LPT
Parallel cable disconnected".
--------------------------------------------
From: "James G. Sack"
On the Access Control page of Network properties, you can choose either
Share level or User level access control. When I set user-level, I
noticed that the guest connect procedure reported the "cannot find
folders on host..." msg and asked for the host name (before failing).
When I set share-level, no such message or prompt for host name occurs
-- but the failure behavior is now that the guest connect procedure
reports "...disconnected".
My speculation is that user-level access control has something to do
with a "Real" network, as opposed to a peer-to peer DCC kludge.
----------------------------------------------------------------------------------------------------------------
From: "T. R. Berta"
You can watch the transfer rates of your DCC connection using the system
monitor (Start -> Accessories -> System Tools -> System Monitor). Bring
up (on the host) the server bytes read / written graphs.
What I've observed is extreme differences in file transfer rates
depending on the type of file requested (or perhaps the Win95
application requesting it?).
Situation: Two PCs connected by laplink serial cables. Using HyperTerm
to demonstrate the line's abilities, can talk at 115,000 baud. They can
do a Zmodem file transfer of a ZIP compressed file at about 9,000
characters per second. That's nearly full bandwidth. Do a Zmondem
transfer of a highly 'compressible' text file at 11,000 cps.
Now run DCC host/guest on the same two machines over the same laplink
serial cable, at same 115,000 baud rate. The highly compressible text
file transfers at an apparent speed of 30,000+ cps! But...the ZIP file
transfers at a DISMAL 1,800 cps. That's right, less than 20% of the
bandwidth.
I'd really like some comments and/or hints from folks more knowledgeable
about ipx/spx protocols and DCC in particular.
If I were just guessing, I'd guess two things from this:
1. Zmodem is a 'streaming' protocol, meaning it doesn't need or wait
for 'acknowlegement' packets from the receiving machine. If all goes
well, you can get the most of your bandwidth. DCC must be highly packet
driven, and have a whale of a lot of overhead.
2. Somewhere buried in DCC is a compression algorithm.
----------------------------------------------------------------------------------------------------------------
From: "T. R. Berta"
You can watch the transfer rates of your DCC connection using the system
monitor (Start -> Accessories -> System Tools -> System Monitor). Bring
up (on the host) the server bytes read / written graphs.
What I've observed is extreme differences in file transfer rates
depending on the type of file requested (or perhaps the Win95
application requesting it?).
Situation: Two PCs connected by laplink serial cables. Using HyperTerm
to demonstrate the line's abilities, can talk at 115,000 baud. They can
do a Zmodem file transfer of a ZIP compressed file at about 9,000
characters per second. That's nearly full bandwidth. Do a Zmondem
transfer of a highly 'compressible' text file at 11,000 cps.
Now run DCC host/guest on the same two machines over the same laplinkserial cable, at same 115,000 baud rate. The highly compressible text
file transfers at an apparent speed of 30,000+ cps! But...the ZIP file
transfers at a DISMAL 1,800 cps. That's right, less than 20% of the
bandwidth.
I'd really like some comments and/or hints from folks more knowledgeable
about ipx/spx protocols and DCC in particular.
If I were just guessing, I'd guess two things from this:
1. Zmodem is a 'streaming' protocol, meaning it doesn't need or wait
for 'acknowlegement' packets from the receiving machine. If all goes
well, you can get the most of your bandwidth. DCC must be highly packet
driven, and have a whale of a lot of overhead.
2. Somewhere buried in DCC is a compression algorithm.
----------------------------------------------------------------------------------------------------------------
From walterl@chch.planet.org.nz Sat Mar 16 03:24:00 1996
Thank for your helpful notes. I have now got a _data _link cable
-- it has y connections at each end -- but it is just so that one
can use 9 or 25 pins i think. I am getting close! I think i
have all the software set (almost?) it still wont connect --
Perhaps it is the wrong cable.
I have tried both parallel and serial options, been through the
trouble shooter . . . hmmm
I have given up the idea of sharing ports and will go for the
28.8 new internal modem -- it would still mean sharing a port,
but not physically -- I presume that can be done?
> DCC will work on the parallel ports although I have not tried it. What =
> do you mean by a double adapter? I'm assuming you mean a Y cable that =
> splits a single port into two (tied in parallel to each other). One =
> thing I noticed when I enabled DCC was that my System Config in Control =
> Panel now indicates a conflict on LPT1. I assume that this is because =
> Win95 knows I have a printer on this port and that DCC could also use =
> LPT1 if I configured it that way. Since I am only using DCC on the =
> serial port (COM2) it does not seem to be causing any problems. The =
Walter Logeman walterl@chch.planet.org.nz
----------------------------------------------------------------------------------------------------------------
From noral@ix.netcom.com Sun Mar 17 16:49:39 1996
Walter Logeman wrote:
>
> Thank for your helpful notes. I have now got a _data _link cable
> -- it has y connections at each end -- but it is just so that one
> can use 9 or 25 pins i think. I am getting close! I think I
> have all the software set (almost?) it still wont connect --
> Perhaps it is the wrong cable.
>
> I have tried both parallel and serial options, been through the
> trouble shooter . . . hmmm
>
> I have given up the idea of sharing ports and will go for the
> 28.8 new internal modem -- it would still mean sharing a port,
> but not physically -- I presume that can be done?
>
> > DCC will work on the parallel ports although I have not tried it. What =
> > do you mean by a double adapter? I'm assuming you mean a Y cable that =
> > splits a single port into two (tied in parallel to each other). One =
> > thing I noticed when I enabled DCC was that my System Config in Control =
> > Panel now indicates a conflict on LPT1. I assume that this is because =
> > Win95 knows I have a printer on this port and that DCC could also use =
> > LPT1 if I configured it that way. Since I am only using DCC on the =
> > serial port (COM2) it does not seem to be causing any problems. The =
>
> Walter Logeman walterl@chch.planet.org.nz
The cable you have sounds like a serial cable with both 9 and 25 pin connectors on each end. You can use it, but you will need a "null
modem" adapter. This is a small device that reverses some of the wires
so the proper pins are connected on the computers. Your modem is not
used in making this DCC connection. However, you cannot use the Dial Up
Networking option at the same time as DCC because they share some
software. You can use the modem with other applications at the same
time a DCC if the other applications do not depend on DUN. Hope this
helps.
Noral Stewart
From lee_slezak@cv.hp.com Mon Mar 18 01:41:34 1996
I am using an HP Omnibook 600c and an HP Vectra XM2, both with 16mb ram
and Win95. I am having major problems connecting with direct cable
connection. I was actually able to connect once using my laplink serial
cable but it was very slow. I beleive all of my software settings are
correct, both systems using Netbui and IPX/SPX. When I set the Omnibook
to be a host and the vectra to be a guest, all I get an attempt to
verify login and password, then a serial line disconnect message. When
I attempt to do the opposite, Omnibook as the guest and vetra as host
(what I really need to do) nothing happens, just an error that the two
cannot connect. Please help! I really need to install some softare
from a CD to my portable... Any suggestions, including other software
packages that will do the job is much appreciated!
Lee Slezak
lee_slezak@cv.hp.com
----------------------------------------------------------------------------------------------------------------
From p@mag.net Mon Mar 18 02:02:34 1996
Every time I try to connect via direct connect parallel connection, I
get the "Cannot find Host Computer" message and am prompted to enter a
host computer name. When I enter my computer name, it retorts "cannot
find shared folders." I am using an authorized cable (parallel
Interlink bi-directional) and have designated shared folders on my
host. I have connected before, and everything worked great, but now
it's virtually impossible. Is there a special setting I need to make
in the Control panel>Network>IPX properties section of the host or
guest computer? Thabks for any replies.
Pete
----------------------------------------------------------------------------------------------------------------
From ynoorani@cbvcp.com Tue Mar 26 06:48:03 1996
I have a laptop running windows 3.1 and a desktop running windows 95.
What software I need on my laptop to connect to the desktop running '95.
Previously I have used interlink.
Y. Noorani
----------------------------------------------------------------------------------------------------------------
From bb@holeinground.com Thu Apr 04 20:39:47 1996
In article <4j83v3$k4o@krel.iea.com>,
ynoorani@cbvcp.com (Yusuf Noorani) wrote:
#I have a laptop running windows 3.1 and a desktop running windows 95.
#What software I need on my laptop to connect to the desktop running
'95.
#Previously I have used interlink.
#
#Y. Noorani
Win95 comes with direct connect (directcc.exe). It's easy to set up,
and works very well. I use it all the time for moving files between a
laptop, and my desktop pc.
ron
----------------------------------------------------------------------------------------------------------------
From genechan@vcn.bc.ca Sun Apr 07 02:35:40 1996
In article <1996Apr4.203957.11433@news.wrc.xerox.com>,
bb@holeinground.com (Bugs Bunny) wrote:
> In article <4j83v3$k4o@krel.iea.com>,
> ynoorani@cbvcp.com (Yusuf Noorani) wrote:
> #I have a laptop running windows 3.1 and a desktop running windows 95.
> #What software I need on my laptop to connect to the desktop running
> '95.
> #Previously I have used interlink.
> #
> #Y. Noorani
>
> Win95 comes with direct connect (directcc.exe). It's easy to set up,
> and works very well. I use it all the time for moving files between a
> laptop, and my desktop pc.
>
> ron
Ummm... true enough, but note that the original poster said he
was running Win 3.1 on the laptop. To run Direct Cable Connection, he
would need to have Win 95 running on both ends of the connection.
Gene H. Chan genechan@vcn.bc.ca
----------------------------------------------------------------------------------------------------------------
From jburkholder@newmedia.net Tue Apr 09 02:44:46 1996
I have found that Symantec's PC Anywhere works great and you can dial
into your system while on the road.
Direct connect is very VERY slow. PCAW is about 3x faster than DC
It is worth the money!
Cheers,
Jeff Burkholder
jburkholder@newmedia.net
----------------------------------------------------------------------------------------------------------------
From jsgard@ix.netcom.com Tue Apr 09 11:04:03 1996
The new version of Laplink should do the trick. Works under both 3.1
& 95.
bb@holeinground.com (Bugs Bunny) wrote:
>In article <4j83v3$k4o@krel.iea.com>,
> ynoorani@cbvcp.com (Yusuf Noorani) wrote:
>#I have a laptop running windows 3.1 and a desktop running windows 95.
>#What software I need on my laptop to connect to the desktop running
>'95.
>#Previously I have used interlink.
>#>#Y. Noorani
>Win95 comes with direct connect (directcc.exe). It's easy to set up,
>and works very well. I use it all the time for moving files between a
>laptop, and my desktop pc.
>ron
J. Scott Gardiner
jsgard@ix.netcom.com
----------------------------------------------------------------------------------------------------------------
From bartsmit@cubix.com Mon Apr 01 09:56:26 1996
tim@tecno.demon.co.uk (Tim Craig) composed the wonderful prose:
>When I connect to a portable using Win95's Direct Cable Connect it says
>something to the effect that it can't locate shared folder on the remote
>computer. I have to respond to its dialog box and tell it the name of the
>remote machine before I can proceed.
>
>What have I set up wrong? Is there a FAQ for DCC within Win95 which
>explains a basic setup for a link between a portable and a desk PC ?
>
>Tim
You'll need to share the hard drive / printer on the host machine.
Open up Network settings from Control Panel and select Add, Service,
MS File sharing. Right-click on your hard drive and select sharing.
Check out www.windows95.com for more details on the procedure for
sharing drives.
Bart...
----------------------------------------------------------------------------------------------------------------
From eskiong@pop.jaring.my Wed Apr 03 23:31:29 1996
Hi Windows95 users,
Need a solution for this problem:
I have Windows95 working in both my Desktop (Pentium 120 machine) and
Notebook (486-66 but without a CD-ROM). I configured both to
communicate using Direct-Cable-Connection having the Desktop as host.
The disks and printer on the host are set for full sharing.
I can then install softwares into the notebook from the CD-ROM in my
desktop using the setup.exe. I can also play games, etc from notebook
using at the CD-ROM of the desktop.
However, when I tried to do Windows Setup from the Control Panel of my
notebook by using the CD-ROm of the desktop, the CD-ROm refused to be
mapped.
Can someone e-mail me the solution at eskiong@pop.jaring.my.
Thanks a lot in advance.
----------------------------------------------------------------------------------------------------------------
From peterm@mckone.loc3.tandem.com Tue May 14 20:58:28 1996
In article <31960359.2598065@192.0.2.3>, mcox@netcom.com (michael cox) writes:
|> you got further than i did...
|> i've done all the same setup stuff you did,
|> & i've never gotten the client machine to log in to the host...
|> ------------------------------------------------------------------------------------------------------
|>
|> danned@bright.net (David Danneberger) wrote:
|>
|> >Hi!
|> >
|> >I have been trying to establish a direct cable connection between my
|> >home computer and laptop. I have run the setup wixard on both
|> >computers, enabled file and printer sharing on the home computer
|> >(host), designated which folders are to be shared and problems still
|> >occur.
|> >
|> >Connection between the two is established, but I get a message to the
|> >effect that no shared files are available. It then asks for the name
|> >of the computer and when I enter the name for my main computer I still
|> >fail to find the shared folders.|> >
|> >Any ideas? I'm not even sure what other information to include to get
|> >an answer to this problem.
|> >
|> >Thanks for any help you can give me.
|> >
|> >David Danneberger
I have direct cable connect working on a parallel cable.
1. You may have to install "dialup network" to get direct cable
connect to work. That was the last thing I did before it
started working.
2. You have to select resources to be shared on the host PC.
I don't remember how I did this, but I bet it's covered in
the help text. Try searching for "share".
Regards,
Peter McKone
----------------------------------------------------------------------------------------------------------------
From francisco.mano@arede.pt Fri May 17 18:40:06 1996
On 14 May 1996 20:58:28 GMT,
Ok, if you have installed all the correct protocols, and shared
Folders, and you have the right cables (laplink 3.0 Parallel or Serial
or a Null modem cable, you should have visible in the Desktop Area the
Network Neighbourhood Icon on the Guest Computer. You donīt need in
the Host though
Donīt ask me Why I just know, that with all the 3 computers I tried
that was necessary or the problem (just like yours) appeared
---
Francisco Marques Mano
Email: francico.mano@arede.pt
Anadia, Portugal
----------------------------------------------------------------------------------------------------------------
From jonk@blkbox.com Sun May 12 22:03:37 1996
danned@bright.net (David Danneberger) wrote:
>Hi!
>I have been trying to establish a direct cable connection between my
>home computer and laptop. I have run the setup wixard on both
>computers, enabled file and printer sharing on the home computer
>(host), designated which folders are to be shared and problems still
>occur.
>Connection between the two is established, but I get a message to the
>effect that no shared files are available. It then asks for the name
>of the computer and when I enter the name for my main computer I still
>fail to find the shared folders.
Hmmm... I got mine to work the first time. Do you have the right
cable hooked up? You should really use a parallel connection; it is
much faster than serial.
Ok, now assuming the link is connected correctly you need to make sure
that you files are shared properly. Double-click the My Computer icon
on the desktop and then highlight the drives you want shared while
holding the ctrl key down. Now click on File, Sharing... and click
the Shared As: radio button then change Access Type to Full. Now you
should be able to hook your computers up with no problem by running
the direct cable connect software.
Note: If you do not have the option Sharing... under File in My
Computer go to Network in the Control Panel and click on the File and
Print Sharing button in the Configuration tab and select both options
for sharing. You'll have to re-boot after doing this.
-Doug Krahmer, ElectraSoft
Contact:
Internet: jonk@blkbox.com
----------------------------------------------------------------------------------------------------------------
From jeffi@sprintnw.com Thu May 16 21:41:48 1996
I have had this same problem and it drove me crazy for a couple of days. The solution to my problem was that I didn't have a protocol loaded. This
only happened to me on one machine out of the 20 or so I've set up.
Be sure to look in the "Network" section of the Control Panel and make
sure you have Client for Microsoft Network installed and that you have at
least a NetBeui protocol loaded. Hopefully this helps!
On Sunday, May 12, 1996, Doug Krahmer wrote...
> danned@bright.net (David Danneberger) wrote:>
> >Hi!
>
> >I have been trying to establish a direct cable connection between my
> >home computer and laptop. I have run the setup wixard on both
> >computers, enabled file and printer sharing on the home computer
> >(host), designated which folders are to be shared and problems still
> >occur.
>
> >Connection between the two is established, but I get a message to the
> >effect that no shared files are available. It then asks for the name
> >of the computer and when I enter the name for my main computer I still
> >fail to find the shared folders.
>
> Hmmm... I got mine to work the first time. Do you have the right
> cable hooked up? You should really use a parallel connection; it is
> much faster than serial.
>
> Ok, now assuming the link is connected correctly you need to make sure
> that you files are shared properly. Double-click the My Computer icon
> on the desktop and then highlight the drives you want shared while
> holding the ctrl key down. Now click on File, Sharing... and click
> the Shared As: radio button then change Access Type to Full. Now you
> should be able to hook your computers up with no problem by running
> the direct cable connect software.
>
> Note: If you do not have the option Sharing... under File in My
> Computer go to Network in the Control Panel and click on the File and
> Print Sharing button in the Configuration tab and select both options
> for sharing. You'll have to re-boot after doing this.
>
> -Doug Krahmer, ElectraSoft
> Contact:
> Internet: jonk@blkbox.com
----------------------------------------------------------------------------------------------------------------
From o.brugger@ieee.org Thu May 30 22:18:09 1996
Hi there,
I had a similiar problem. The solution was, envoke Tweak UI and make
the network icon to apear on the desktop.
Then - for me - everything worked ok.
Maybe that helps.
BTW: Information from MS Knowledge Base (Support area on
www.microsoft.com)
Greetings
Oli
> > >Hi!
> >
> > >I have been trying to establish a direct cable connection between my
> > >home computer and laptop. I have run the setup wixard on both
> > >computers, enabled file and printer sharing on the home computer
> > >(host), designated which folders are to be shared and problems still
> > >occur.
> >
> > >Connection between the two is established, but I get a message to the
> > >effect that no shared files are available. It then asks for the name
> > >of the computer and when I enter the name for my main computer I
still
> > >fail to find the shared folders.
----------------------------------------------------------------------------------------------------------------
From pleonard@cybercom.net Mon May 13 02:03:48 1996
In article ID <3190f81a.29797192@news.bright.net>, danned@bright.net (David
Danneberger) writes:
>I have been trying to establish a direct cable connection between my
>home computer and laptop. Connection between the two is established, but I get a message to the
>effect that no shared files are available. Any ideas?
If you are using Tweakui from the Power tools and have removed the Network
Neighborhood icon from the desktop, you need to restore it for DCC to work.
----------------------------------------------------------------------------------------------------------------
From mohn@are.berkeley.edu Mon May 13 03:01:51 1996
pleonard@cybercom.net (Phil Leonard) wrote:
>In article ID <3190f81a.29797192@news.bright.net>, danned@bright.net (David
>Danneberger) writes:
>>I have been trying to establish a direct cable connection between my
>>home computer and laptop. Connection between the two is established, but I get a message to the
>>effect that no shared files are available. Any ideas?
>If you are using Tweakui from the Power tools and have removed the Network
>Neighborhood icon from the desktop, you need to restore it for DCC to work.
Ordinarily I would defer to Phil's expertise, because he is one of the
most knowledgeable and active participants in this forum, one who has
helped a lot of people over a long time. But this is not correct. I
run DCC between my main machine and my notebook, and do not have
network neighborhood on my main machine's desktop. I'm pretty sure
I've run DCC with NN removed from both machines' desktops, since it
doesn't seem to do anything - clicking on anything gets a message that
there are no network resources. That may be a function of my only
setting my CD-ROM and a very select set of directories as shared.
I think David may have forgotten to set sharing permissions on his
machines. To do this you set file sharing enabled in the Network
Control Panel applet, and then "Sharing" shows up as an option when
you right click a drive or folder.
Craig Mohn
mohn@are.berkeley.edu
----------------------------------------------------------------------------------------------------------------
From pleonard@cybercom.net Mon May 27 00:29:18 1996
>>In article ID <3190f81a.29797192@news.bright.net>, danned@bright.net (David
>>Danneberger) writes:
>>>I have been trying to establish a direct cable connection between my
>>>home computer and laptop. Connection between the two is established, but I get a message to the
>>>effect that no shared files are available. Any ideas?
I wrote;
>>If you are using Tweakui from the Power tools and have removed the Network
>>Neighborhood icon from the desktop, you need to restore it for DCC to work.
In article ID <3196a46e.7653168@agate>, mohn@are.berkeley.edu (Craig Mohn)
writes:
>Ordinarily I would defer --- --- But this is not correct.
Well, Craig, it happened to me, and I read about it from Microsoft Tech
support, and it happened to be this person's problem. First I'll quote his
e-mail response and then I'll quote Microsoft Tech support:
----------------
You were right --- It was the Network Neighborhood icon. I restored it on
both computers and everythng worked well.
----------------
Are you using the Tweak UI applet from the Powertools? If you are, start
Tweak UI, click the Desktop icon, and then click the Network check box to
select it. That should do it. If you aren't using Tweak UI, make sure
that you aren't trying to connect to one computer using another with the
same name. Make sure you have different computer names on each, but the
same Workgroup.
Hope this helps!
Kirk Leeson
Microsoft AnswerPoint
Desktop Systems
----------------------------------------------------------------------------------------------------------------
From mohn@are.berkeley.edu Mon May 27 02:28:26 1996
pleonard@cybercom.net (Phil Leonard) wrote:
>>>In article ID <3190f81a.29797192@news.bright.net>, danned@bright.net (David
>>>Danneberger) writes:
>>>>I have been trying to establish a direct cable connection between my
>>>>home computer and laptop. Connection between the two is established, but I get a message to the
>>>>effect that no shared files are available. Any ideas?
>I wrote;
>>>If you are using Tweakui from the Power tools and have removed the Network
>>>Neighborhood icon from the desktop, you need to restore it for DCC to work.
>In article ID <3196a46e.7653168@agate>, mohn@are.berkeley.edu (Craig Mohn)
>writes:
>>Ordinarily I would defer --- --- But this is not correct.
>Well, Craig, it happened to me, and I read about it from Microsoft Tech
>support, and it happened to be this person's problem. First I'll quote his
>e-mail response and then I'll quote Microsoft Tech support:
>----------------
>You were right --- It was the Network Neighborhood icon. I restored it on
>both computers and everythng worked well.
>----------------
>Are you using the Tweak UI applet from the Powertools? If you are, start
>Tweak UI, click the Desktop icon, and then click the Network check box to
>select it. That should do it. If you aren't using Tweak UI, make sure
>that you aren't trying to connect to one computer using another with the
>same name. Make sure you have different computer names on each, but the
>same Workgroup.
Okay, so I checked all 4 possible combinations on my two machines.
1) No Network Neighborhood on either machine's desktop
Guest can't find shared folder on host
2) Network Neighborhood on host's desktop , not on guest's desktop
Guest can't find shared folder on host
3) On guest not on host Works fine4) On both
Works fine
So it appears that the network neighborhood must be on the guest
machines desktop, but is optional on the host machine's. I was
mistaken when I said I thought I recalled it working with the icon on
neither machine's desktop, but I was correct that it didn't need to be
on both.
However, I have noticed 2 other interesting oddities about Direct
Cable Connect:
1) No matter which of the 4 combinations listed above that I try,
clicking on "Entire Network" (or whatever it's called, I packed away
my notebook so I have to rely on my memory, which is demonstrably
imperfect) under Net Neighborhood yields a message that the network
isn't visible. Clicking on the show host folders button on the DCC
box works fine.
2) After I terminate the DCC session normally, the host still thinks
that the guest is sharing its folders. When I shut down windows, it
warns me that there is 1 user sharing folders, and asks if I want to
shut down anyway. Is this a security problem in any way if I were to
log onto TCP/IP connection without restarting windows? I normally set
all folders to nonshared after ending a DCC session between my
notebook and desktop machines.
Craig Mohn
mohn@are.berkeley.edu
----------------------------------------------------------------------------------------------------------------
From danned@bright.net Mon May 13 12:39:33 1996
On Mon, 13 May 1996 02:03:48 GMT, pleonard@cybercom.net (Phil Leonard)
wrote:
>If you are using Tweakui from the Power tools and have removed the Network
>Neighborhood icon from the desktop, you need to restore it for DCC to work.
BINGO! I think you have it! I remove the Network Neighborhood icon
a long time ago and have done everything right, as far as I can tell
with the setup. Thanks for the tip. I'm going to try it now!
David
----------------------------------------------------------------------------------------------------------------
From jgarrett@magicnet.net Mon Jun 03 04:25:35 1996
Maybe someone has an answer to this one. I have direct cable connection
working between a Toshiba 1950 laptop and a Dell computer with no problems.
When I try to connect it to a computer with an AMI Super Voyager motherboard
it acts as if the connection cable did not exist for the parallel connection
but not the serial connection. AMI is of no help. I suspect something is amiss
with the configuration of the SMC peripheral controller on the motherboard.
Cables have been swapped and all the normal stuff tried.
Help and thanks!
jgarrett@magicnet.net
----------------------------------------------------------------------------------------------------------------
From awillims@iol.ie Sun Apr 07 15:25:56 1996
I'm trying to hook two Dell Latitudes together using the direct cable
connection feature in W95. I'm using my laplink parallel cable to the
two LPT ports. When I kick it off, they see each other, the guest
tries to log on to the host, and then is disconnected.
Has anyone seen this before???
Gavin
----------------------------------------------------------------------------------------------------------------
From kotto@comp.uark.edu Sun Apr 07 20:26:22 1996
>I'm trying to hook two Dell Latitudes together using the direct cable
>connection feature in W95. I'm using my laplink parallel cable to the
>two LPT ports. When I kick it off, they see each other, the guest
>tries to log on to the host, and then is disconnected.
>
>Has anyone seen this before???
Yes, I've seen this. Make sure that some common networking protocol is
installed on both systems, like IPX or TCP/IP. It seems that with the
direct cable connection, the PCs actually link up as a network. I generally
use IPX because I can also play multi-player games using that protocol.
One thing I've noticed though is that the server PC is terribly slow (the
PC I was using was a P120 w/16MB RAM for the server and a P133 w/8MB RAM for
the client; the client was fast but the server was slow). Does anyone know
why? Anyway, I used a parallel data transfer cable on mine as well. The data
transfer was pretty fast. The only problem was the server speed (for playing
games).
Kevin
----------------------------------------------------------------------------------------------------------------
From genechan@vcn.bc.ca Sun Apr 21 23:52:15 1996
In article <4k9bt0$hos@wizard.uark.edu>,
kotto@comp.uark.edu (Kevin Otto) wrote:
> Yes, I've seen this. Make sure that some common networking protocol is
> installed on both systems, like IPX or TCP/IP. It seems that with the
> direct cable connection, the PCs actually link up as a network. I generally
> use IPX because I can also play multi-player games using that protocol.
> One thing I've noticed though is that the server PC is terribly slow (the> PC I was using was a P120 w/16MB RAM for the server and a P133 w/8MB RAM for
> the client; the client was fast but the server was slow). Does anyone know
> why? Anyway, I used a parallel data transfer cable on mine as well. The data
> transfer was pretty fast. The only problem was the server speed (for playing
> games).
Before I read your post, I had been wondering how far the Direct
Cable Connection facility went in behaving "like a network". So I
experimented a bit. The "Hearts" card game that comes with Win 95 has a
"network" mode available. I tried it, and to my surprise, it works!
Next, I wondered what would happen if I installed the TCP/IP
protocol. I did that, and whaddya know: I assigned an IP address to
each PC, and was able to run a Web server on one and a Web browser on
the other. TCP/IP utilities like ping and tracert also worked.
Surprised me, I must say.
This morning, fooling around some more, I fired up "Ultimate
DOOM" in IPX network mode, and it works too.
Reading your note this afternoon is the first "printed" mention
I've seen anywhere that DCC had these capabilities.
A "poor man's LAN", for $14 (the price of the parallel file
transfer cable)!
Gene H. Chan genechan@vcn.bc.ca
----------------------------------------------------------------------------------------------------------------
From karini@aksi.net Mon Apr 08 15:21:48 1996
awillims@iol.ie (Gavin Williams) wrote:
>I'm trying to hook two Dell Latitudes together using the direct cable
>connection feature in W95. I'm using my laplink parallel cable to the
>two LPT ports. When I kick it off, they see each other, the guest
>tries to log on to the host, and then is disconnected.
>
>Has anyone seen this before???
>
>TIA
>
>Gavin
Yes, my experience was that BOTH machines need to have ALL protocals
(the same protocals) enabled. Before I could get both machines
operating properly to share files and printers I used this:
Under Network -> Configuration
Client for MS Networks
Dial up Adapter
IPX/SPX-compatable Protocal
NetBEUI
TCP/IP
File and printer shareing for MS Networks
(You don't have to have the TCP/IP for file and printer sharing but
you do have to have the dial up adapter due to bindings)
Note - BOTH machines (host and guest) have to have the same protocals
enabled.
At least that has been my experience. I have my two computers (a P133
and a 386DX) both running Win95 and connected via the Direct Cable
mode using a parallel cable on LPT1 on the guest box (the 386) and on
LPT2 on the host (the P133). Everything works great and I can use
the printer off the host and move files etc....
Good luck,
Karin Isberg
karini@aksi.net
Miami, FL (USA)
----------------------------------------------------------------------------------------------------------------
From tim@tecno.demon.co.uk Tue Apr 09 12:02:34 1996
I'm sure someone has figured out how to use Direct Cable Connect in Win95
but its baffling me. To the extent that I have managed to get it to work it
seems really good. Especially when used with the briefcase icon though I
find it better to have the brief case on the host/desktop machine and leave
the lid down on the portable. Maybe this is the wrong strategy - tell me.
1. How do I kick-off the host by putting it in the startup group but
avoiding the need to hit the 'connect' button.
2. Why does the client computer say "Unable to Locate the shared folders"
even though they have been defined on the host, abnd goes on to say "type
in the name of the remote computer' whereupon it DOES manage to locate the
shared folders. What's going on here?
3. What is the 'LM Announce' and 'Browser' all about?
4. Should IPX be set (under Bindings) to Clients for Microsoft Networks AND
File and Printer Sharing for Microsoft Networks?
5. Is there a decent file or FAQ which explain the various implementations
of Direct Cable Connections?
6. Can I use a pair of ethernet cards on the two connected machines to
acheive a very fast communations speed?
7. If I can use a pair of ethernet cards (one PCI and one PCMCIA for the
portable) can the portable access resources on the desktop machine such as
the modem? Is it worth bothering with this idea?
----------------------------------------------------------------------------------------------------------------
From medgmhs@ttuhsc.edu Thu Apr 11 15:19:15 1996
I am trying to set up a direct cable connections. Is is correct to say that
the parallel connection is fastest/most realiable?
How do you physically connect the two computers when each has a printer on
the parallel connection? Is there a Y-adaptor or something like that? In
other words, what is the best way to connect the machines?
Please reply by email.
Max H Schubert
medgmhs@ttuhsc.edu
----------------------------------------------------------------------------------------------------------------
From noral@ix.netcom.com Thu Apr 11 21:25:25 1996
Max H Schubert wrote:
>
> I am trying to set up a direct cable connections. Is is correct to say that
> the parallel connection is fastest/most realiable?
>
> How do you physically connect the two computers when each has a printer on
> the parallel connection? Is there a Y-adaptor or something like that? In
> other words, what is the best way to connect the machines?
>
> Please reply by email.
>
> Max H Schubert
> medgmhs@ttuhsc.edu
I too would like to know if there is a way to use a parallel connection
if even one of the computers has a printer connected and that computer
has only one parallel port. I am currently using a serial connection,
but understand the parallel is much faster. One warning once you
establish the DCC. Do not try to use DUN to access the internet at the
same time you use DCC. They share some common software that will not
allow DUN and DCC to operate at the same time. If you try to open
DUN while DCC is active, you will get a message that the port is already
open though it actually is not.
Noral Stewart
From karma@metrolink.net Sat Apr 13 00:53:41 1996
Can someone please Email me with some tips on getting Direct Cable Connection
to work. All I want to do is connect two computers via null modem cable
(which I know works perfectly). I want the guest computer to have complete
access to the host computer with no need for any sort of passwords at all.
All I want to do is transfer files between the two. Nothing fancy. It seems
the Direct Cable Connection app is a little more than what I need, but it's
all I got. I know almost nothing about networks. If someone has the patience
to explain this procedure (pretend I'm four years old) I would greatly
appreciate it. Or if not, can you point me in the direction of a FAQ or book
that can help.
My problems occur when it asks for passwords and won't let me define a
password list. It connects but then doesn't recognize the host computer's
name. I don't care about names and passwords. I just want to connect them.
Thanks in advance.
Karma Roach
----------------------------------------------------------------------------------------------------------------
From tim@tecno.demon.co.uk Wed Apr 24 08:28:48 1996
I have Direct Cable Connection installed to connect from a desktop to a
laptop. the Desktop also requires TCP/IP proptocol. It seems that when this
is installed in addition to DCC it causes the latter to be unable to locate
the shared folders on the remote machine at the initial connection phase.
After the name of the remote machine is typed in it work OK.
Anyone got any more experience on this anomaly.
Tim
----------------------------------------------------------------------------------------------------------------
From genechan@vcn.bc.ca Wed May 01 03:18:53 1996
In article <31809356.4306347@news.demon.co.uk>,
tim@tecno.demon.co.uk (Tim Craig) wrote:
> I have Direct Cable Connection installed to connect from a desktop to a
> laptop. the Desktop also requires TCP/IP proptocol. It seems that when this
> is installed in addition to DCC it causes the latter to be unable to locate
> the shared folders on the remote machine at the initial connection phase.
> After the name of the remote machine is typed in it work OK.
>
> Anyone got any more experience on this anomaly.
After I installed Direct Cable Connection initially (without
TCP/IP being installed), it connected successfully without any extra
prompting after clicking the "connect" button in the dialog box.
I subsequently installed the TCP/IP Protocol as well as the
"standard" Network Components installed by the Direct Cable Connection
installation procedure. (I installed TCP/IP as a bit of an experiment
to see what would happen.)
Anyway, DCC continues to work okay, but as you have commented,
there's now an extra step after clicking the "connect" button": I'm now
prompted for the name of the host PC. One thing I am going to try, but
haven't yet, is going into Control Panel : Network : Configuration :
NetBEUI : Properties : Advanced , and checking the box labelled "Set
this protocol to be the default protocol", to see if that will "fix" the
problem.
Gene H. Chan genechan@vcn.bc.ca
----------------------------------------------------------------------------------------------------------------
From jjdavis@xnet.com Mon May 06 17:05:31 1996
On Tue, 30 Apr 1996 20:18:53 -0700, genechan@vcn.bc.ca (Gene H. Chan)
wrote:
>In article <31809356.4306347@news.demon.co.uk>,
>tim@tecno.demon.co.uk (Tim Craig) wrote:
>> I have Direct Cable Connection installed to connect from a desktop to a
>> laptop. the Desktop also requires TCP/IP proptocol. It seems that when this
>> is installed in addition to DCC it causes the latter to be unable to locate
>> the shared folders on the remote machine at the initial connection phase.
>> After the name of the remote machine is typed in it work OK.
>> >> Anyone got any more experience on this anomaly.
> After I installed Direct Cable Connection initially (without
>TCP/IP being installed), it connected successfully without any extra
>prompting after clicking the "connect" button in the dialog box.
> I subsequently installed the TCP/IP Protocol as well as the
>"standard" Network Components installed by the Direct Cable Connection
>installation procedure. (I installed TCP/IP as a bit of an experiment
>to see what would happen.)
> Anyway, DCC continues to work okay, but as you have commented,
>there's now an extra step after clicking the "connect" button": I'm now
>prompted for the name of the host PC. One thing I am going to try, but
>haven't yet, is going into Control Panel : Network : Configuration :
>NetBEUI : Properties : Advanced , and checking the box labelled "Set
>this protocol to be the default protocol", to see if that will "fix" the
>problem.
I had TCP/IP installed on both laptop and desktop machines (because I
need them for PPP access, etc.) before I installed DCC. So I thought it
was just a bug with DCC and didn't pick up that it was related to
TCP/IP. Please let me know if any playing with "Default" protocols
works. I don't so much mind having to enter the machine name at login,
but it also seems to make the connection a little flakier, sometimes not
being able to explore deep in folders, not being able to access files to
synchronize briefcase, etc.
any help appreciated.
Jeff Davis
jjdavis@xnet.com
----------------------------------------------------------------------------------------------------------------
From zykur@earthlink.net Mon Apr 29 03:19:32 1996
OK, here it is all:
Direct Cable Connect used to work...and well at that.
I didn't use it for a while and have recently had the need. I hooked
the cable to my laptop and then to my desktop, just like I always did,
but this time, as it is verifying username and password, id cuts out
and disconnects.
The host(desktop) keeps waiting while the guest(laptop) gives a
disconnected message.
I then (for other reasons) reinstalled 95 on the desktop....and tried
again.......nothing....same message.
I dont recall ever specifying a username and passoword....but I
suspect since neither the host or guest have password protect enabled,
that wouldnt matter.
Any ideas on this one???
Please email responses.....and thank you in advance.
Christopher Prouty
p.s. I also tried switching the host and guest assignments...no luck.
----------------------------------------------------------------------------------------------------------------
From dbloem@solair1.inter.nl.net Wed May 01 07:29:20 1996
zykur@earthlink.net (Zykur) wrote:
>OK, here it is all:
>Direct Cable Connect used to work...and well at that.
>I didn't use it for a while and have recently had the need. I hooked
>the cable to my laptop and then to my desktop, just like I always did,
>but this time, as it is verifying username and password, id cuts out
>and disconnects.
>The host(desktop) keeps waiting while the guest(laptop) gives a
>disconnected message.
>I then (for other reasons) reinstalled 95 on the desktop....and tried
>again.......nothing....same message.
>I dont recall ever specifying a username and passoword....but I
>suspect since neither the host or guest have password protect enabled,
>that wouldnt matter.
>Any ideas on this one???
>Please email responses.....and thank you in advance.
>Christopher Prouty
>p.s. I also tried switching the host and guest assignments...no luck.
I just had the same problems this weekend and now know what is wrong:
Make sure that on both computers you have the dial-up adapter as your
network card. Then make sure you both run the same protocol. I use IPX
and Netbeui and Windows client blabla and bind these protocols to the
adapter too!!. I had a dial up adapter installed and these protocols
including tcp/ip but I had only the tcp/ip binded to the adapter. The
other two, ipx/netbeui were binded to my real network card.
When this was fixed, I all worked and no disconnections anymore
Good luck
Danny
dbloem@dp.dpfinance.nl
----------------------------------------------------------------------------------------------------------------
From jjdavis@xnet.com Sat May 04 01:33:50 1996
I am using direct cable connect to transfer files between by compaq
contura 486 100Mhz laptop and my Acer ACROS P75 desktop using the
serial port on each machine. I assumed serial would be slow, but this
is ridiculous (approximately 10 minutes per MB). Both ports have UARTs
and both are configured hardware handshake and max speed. What am I
doing wrong, or is this about what I should expect? What should I
expect for serial?
any help appreciated.
Jeff Davis
jjdavis@xnet.com
----------------------------------------------------------------------------------------------------------------
From wsoon@primenet.com Sat May 04 14:10:01 1996
That's about ridiculously right for serial DCC !!! I had to use a
parallel laplink cable before transfer speeds were reassuring enough
to convince me one of my machines did not hang. I used a standard
Laplink compatible parallel cable; I think if your parallel ports are
enhanced you can try the super turbo whatever EPP cable.
But if you want to transfer anything in this lifetime, don't use
serial with DCC.
-Bill
jjdavis@xnet.com (Jeff Davis) wrote:
>I am using direct cable connect to transfer files between by compaq
>contura 486 100Mhz laptop and my Acer ACROS P75 desktop using the
>serial port on each machine. I assumed serial would be slow, but this
>is ridiculous (approximately 10 minutes per MB). Both ports have UARTs
>and both are configured hardware handshake and max speed. What am I
>doing wrong, or is this about what I should expect? What should I
>expect for serial?
>
>
>any help appreciated.
>
>
>Jeff Davis
>jjdavis@xnet.com
----------------------------------------------------------------------------------------------------------------
wsoon@primenet.com http://www.primenet.com/~wsoon/
From clab@gpnet.it Sat May 11 10:26:52 1996
>I am using direct cable connect to transfer files between by compaq
>contura 486 100Mhz laptop and my Acer ACROS P75 desktop using the
>serial port on each machine. I assumed serial would be slow, but this
>is ridiculous (approximately 10 minutes per MB). Both ports have UARTs
>and both are configured hardware handshake and max speed. What am I
>doing wrong, or is this about what I should expect? What should I
>expect for serial?
10' per MB it's about the speed of a 14.400 bps modem.
With a direct connection you should be able to get a 115.200 bps.
For this you need buffered UARTs (of course you have UARTs, but which
one? Buffered models are called 16550).
You need a good quality cable too.
Anyhow, if you can, use a connection trought the parallel port.
Hope it helps,
Corrado.
Corrado Labinaz
Vicenza (Italy)
internet: clab@gpnet.it
----------------------------------------------------------------------------------------------------------------
From danned@bright.net Thu May 09 20:51:46 1996
I have been trying to establish a Direct Cable Connection between my
laptop and my desktop computer. I have run the Setup Wizard on both
computers and have designated certain folders as shared. I have setupfolder and printer sharing under Networking.
The two computers establish a connection and then I get the following
message:
Direct Cable Connection was unable to display the shared folders of
the host computer. To see the shared folders, type in the name of the
host computer."
I type in the anme which I gave the desktop when I first setup Dial-Up
Networking. The computer looks for shared folders and then I get:
"Cannot find the host computer."
Any ideas? Please!
David Danneberger
----------------------------------------------------------------------------------------------------------------
From tim@tecno.demon.co.uk Fri May 10 11:27:40 1996
This looks like the problem I had; and still have partially.
It seems that you have TCP/IP or some other protocol in the system and if
you go into Network Setup (Control Panel) you should specify that only IPX
has bindings to 'File & Print Sharing' and 'Client for MS Networks'. My bet
is that you will find your other protocol is bound to these later items.
That said, it will still ask for the name of the remote machine when you
connect and you can if you wish enter a name at this point. I found that if
I just clicked 'cancel' the box went away and the DCC link worked fine.
It's definately a messy bug though. I think maybe that MicroSoft want to
make it as hard as possible for the rest of us to use TCP/IP.
Tim
----------------------------------------------------------------------------------------------------------------
From j.heuft@pi.net Sun May 12 08:33:32 1996
Greetings,
I've got a little problem with the Direct Cable Connection. I
connected my computer with another computer using a 0-modem.
When the other computer logs into my computer everything works
perfect. But when I log into the other computer I receive an
error-message that says "The folder 'DX66' does not exist". DX66 is
the name of the other computer. I get the same error message when I
click "View Host". I do have some folders shared on the other computer
and I can access them by connecting to them in Windows 95 Explorer.
How can I correct this problem ?
If you know please E-mail me at j.heuft@pi.net
Thanks,
Jasper Heuft
----------------------------------------------------------------------------------------------------------------
From humenik@nscl.msu.edu Tue May 21 10:14:42 1996
In article <4nlqgb$mq5@ccshst05.uoguelph.ca>, sbaris@uoguelph.ca says...
>
>I have 2 pc's, both running Windows 95, and I have a bi-directional
>parallel cable connecting both. I have them set up as host and guest.
>The damn thing keeps hanging on the "verifying User Name and Password"
>screen.
>Something about an authorized user list?...Any ideas?
>
Are your Win95 UserNames and passwords identical on both machines?
Including upper/lower case? I did this as a simplifying first step in
connecting my two machines.
My first actual attempt at DCC was with a store-bought generic "Laplink"
parallel cable. Could not even get to the Verifying User Name stage.
Upon taking it back to the dealer, we compared the pin-outs with his
known-good Laplink cable his shop techs used. Although they were the same
on the data lines, the store-bought cable was missing five straigh-thru
connections. Armed with this pinout info, after getting my money back I
made my own copy of his cable...and it worked the first time.
Although this may not solve your particular problem, for other users of
this nifty Win95 utility here are the correct pinouts for a parallel
DCC cable (DB-25male on both ends):
1>1; 2>15; 3>13; 4>12; 5>10; 6>11; .. 10>5; 11>6; 12>4; 13>3; 14>14;
15>2; 16>16; 17>17; 25>25;
Since one of my machines has a plain-Jane non-ECP parallel port this cable
only supports the 4-bit protocol. Still, it is nice to be able to move
files onto my new hard disk from my old machine. Not as fast as
Ethernet... but it's a far cry from Kermit.
Alas, if only my Guest could share the Host's networked printers ...
Greg Humenik
----------------------------------------------------------------------------------------------------------------
From mohn@are.berkeley.edu Wed Jun 05 15:34:54 1996
Paul Crisostomo wrote:
>Has anyone gotten this thing to work? I've tried using a parallel cable >connection to no avail. I've tried setting up one computer as a host and
>the other as a guest and vice versa. I've shared directories. I've
>installed dial up adapter. And I also have installed TCP/IP, NetBIOS,
>and IPX stuff. Nothing lets it work. Any ideas? Thanks
Make sure your parallel cable has the correct pinout, any "laplink"
cable should be okay. Make sure the parallel port is configured the
same (normal, EPP,ECP,ECP+EPP) on both machines. Make sure the "guest"
machine has Network Neighborhood visible on it's desktop. If this
doesn't work go into windows setup and uninstall then reinstall DCC.
Good luck
Craig Mohn
mohn@are.berkeley.edu
----------------------------------------------------------------------------------------------------------------
From epsilon@sibyl Thu Jun 06 05:08:20 1996
It there any way in which I can connect my Windows 95 with my Windows 3.1
using Direct Cable Connection.
----------------------------------------------------------------------------------------------------------------
>>I have installed the dial-up server from the MS Plus CD and although I
>>can get the remote computer to answer the telephone and apparently
>>log-in I can't see were to go from here. Once the computers are
>>conmnected how do I get the remote computers files visible from the
>>dialing-in computer.
The answer is to go to the "RUN" command and
type:RUN\\"netBIOSname" where "netBIOSname" is the netBIOS name
of the remote computer you have dialed into.
I have to warn you, I never actually tried this, but I read it in another
newsgroup when I experienced the same problem you did.
On the dialing in machine, (the one that has called the host),
Go to the START menu, select "RUN"
Type "run\\netBIOS"
The netBIOS is the name of the host computer in its networking setup.
I believe by default it is "my computer" to change it, under the start
menu, select:settings, control panels, network, identity. You can call
it anything you like, but I suggest you keep it short to minimize the
amount of typing when you log into it. Make sure that you have enabled
"sharing" on the host machine's drives and/or folders. You will find that
under "properties" for the respective drives or folders. If my sources
are correct you should be able to see the shared folders or drives for the
host machine from the guest that has dialed into it.
Jon Miller
----------------------------------------------------------------------------------------------------------------
From: bstratma@evansville.net (B Stratman)
The netBIOSname is the name of your computer as entered in the Identification
tab of the Network control panel applet (let's say the computer you are dialing
into is named MY_HOST). \\netBIOSname is the Universal Naming Convention (UNC)
for network resources. If you click the START button you will see a Run
command. If you "run" \\MY_HOST you will see the resources you have shared on
the MY_HOST computer. You must explicitly declare resources on the machine your
are calling as sharable (use the "sharing" option when you right-click printers,
disk volumes, disk directories, etc.).
----------------------------------------------------------------------------------------------------------------
From: "Arne Stockman"
I bought a new computer with win 95 and set up a DCC connection to my old
machine, all worked OK except for that it was unidirectional. Then I
reconfigured my disk on the new computer and reinstalled win 95 from the CD that
I got whith the new computer. The win 95 was not exactlly the same version as
the version originally installed. I'we learned that the version originally
installed was called win 95 a and the version on the CD was win 95b. Anyway, I
never have been able to get DCC from win 95 b to work. After some tries I gave
up with win 95 b on my new computer and installed win 95 a wich I had on the CD
from my old computer. Then DCC worked fine again. I made a new test with win 95
b on my old computer as I reconfigure the disk on that computer too. The same
result!
Other DCC related sites
These sites are courtesy of Frank J. Kime Jr.
Windows 95 to
Windows NT (workstation or server)
edl@tecno.demon.co.uk
