Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

File Transfer Lockups on 333MHz PCs

1 view
Skip to first unread message

Les Coates

unread,
Sep 25, 1998, 3:00:00 AM9/25/98
to
On 25 Sep 1998 00:31:29 GMT, Les Coates wrote:
'Just wanted to add: All relevant files are updated and current
(including the modem .inf and PCAW32 to V8.02) and all settings
appear to be correct, as everything except file transfer works great.

Larry McDowall (Symantec)

unread,
Sep 25, 1998, 3:00:00 AM9/25/98
to
Hello Les,

Thank you for using our online support groups.

On 25 Sep 1998 00:31:29 GMT, Les Coates wrote:

>In our business, we use multiple versions of PCAW on a variety of
>machines and all work very nicely. The only outstanding problem is
>as follows: On our newest PC, a Dell Dimension XPS D333, every
>attempt at using the file transfer capability locks up the
>application (at the last button click to actually transfer the file).
>All other remote control functions work perfectly. This occurs when
>connected to any host version. Any suggestions?

Does this issue occur if a different remote connects to any of these
hosts and performs file transfer?

It appears that this issue occurs only when one remote connects to any
host. If so, most likely the file transfer files that are part of
pcANWHERE32 on the remote may be corrupted.

I recommend uninstalling pcANYWHERE32, clean booting so that nothing
else is running (this is important), and then reinstalling it. When
you clean boot, the only things that should be left on the
CTRL+ALT+DEL Close Program list will be Explorer and SysTray; end task
on all other items there. If the issue continues after that, then most
likely something else beyond pcANYWHERE32 is causing this issue.

Please let us know if this recommendation does not resolve the issue.
---------------------------
Larry McDowall
Symantec Online Support
Symantec Corporation

Please continue to post your messages to the public discussion groups as Symantec does not provide support via private email.

If you have difficulty getting a response, please read the following article:

Tips on Using Symantec's Online Tech Support Discussion Groups
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414

For free technical support newsletters, Knowledge Base support articles, our Online Support Genie, and FAQs, visit our technical support page:

Technical Support
http://www.symantec.com/techsupp/
---------------------------

Larry McDowall (Symantec)

unread,
Sep 25, 1998, 3:00:00 AM9/25/98
to
Hello Les,

Thanks for this additional information. Please see my first reply to
your original message on how to resolve this issue.

On 25 Sep 1998 00:47:16 GMT, Les Coates wrote:

>On 25 Sep 1998 00:31:29 GMT, Les Coates wrote:

>'Just wanted to add: All relevant files are updated and current
>(including the modem .inf and PCAW32 to V8.02) and all settings
>appear to be correct, as everything except file transfer works great.

Les Coates

unread,
Sep 27, 1998, 3:00:00 AM9/27/98
to
On Fri, 25 Sep 1998 19:11:11 GMT, Larry McDowall (Symantec) wrote:
> Hello Les,
>
> Thank you for using our online support groups.
>
> On 25 Sep 1998 00:31:29 GMT, Les Coates wrote:
>
> >In our business, we use multiple versions of PCAW on a variety of
> >machines and all work very nicely. The only outstanding problem is
> >as follows: On our newest PC, a Dell Dimension XPS D333, every
> >attempt at using the file transfer capability locks up the
> >application (at the last button click to actually transfer the file).
> >All other remote control functions work perfectly. This occurs when
> >connected to any host version. Any suggestions?
>
> Does this issue occur if a different remote connects to any of these
> hosts and performs file transfer?
>
> It appears that this issue occurs only when one remote connects to any
> host. If so, most likely the file transfer files that are part of
> pcANWHERE32 on the remote may be corrupted.
>
> I recommend uninstalling pcANYWHERE32, clean booting so that nothing
> else is running (this is important), and then reinstalling it. When
> you clean boot, the only things that should be left on the
> CTRL+ALT+DEL Close Program list will be Explorer and SysTray; end task
> on all other items there. If the issue continues after that, then most
> likely something else beyond pcANYWHERE32 is causing this issue.
>
> Please let us know if this recommendation does not resolve the issue.
> ---------------------------
> Larry McDowall
> Symantec Online Support
> Symantec Corporation
>
Larry, the following are answers to your questions, plus some
additional info:

#1. All our hosts work fine when connected to other remotes. (These
hosts are 133MHz machines from Dell and others.)

#2. I also verified this particular copy of the software by trying
it on another machine. It worked fine.

#3. I had already done the recommended uninstall, CLEAN reboot, and
reinstall procedure prior to leaving you the first e-mail.

#4. All our machines are similarly configured, with Win95b/fat32,
appropriate drivers, updates, etc installed from scratch, eliminating
any potential problems with all the Dell doodads that come preloaded
on these things. The only one we're having problems with is the
higher speed (333MHz) unit.

What suggestions do you have for us?

Dana Burian (Symantec)

unread,
Sep 27, 1998, 3:00:00 AM9/27/98
to
On 27 Sep 1998 03:53:42 GMT, Les Coates <xx.co...@internetMCI.com>
wrote:

Hello Les.

>#1. All our hosts work fine when connected to other remotes. (These
>hosts are 133MHz machines from Dell and others.)
>
>#2. I also verified this particular copy of the software by trying
>it on another machine. It worked fine.
>
>#3. I had already done the recommended uninstall, CLEAN reboot, and
>reinstall procedure prior to leaving you the first e-mail.
>
>#4. All our machines are similarly configured, with Win95b/fat32,
>appropriate drivers, updates, etc installed from scratch, eliminating
>any potential problems with all the Dell doodads that come preloaded
>on these things. The only one we're having problems with is the
>higher speed (333MHz) unit.
>
>What suggestions do you have for us?

I would recommend going over the documents listed below to verify that
there is not a hardware issue and to attempt to find what may be
causing the issue. All documents are located on our Knowledge Base
at:

Title: 'Resolving IRQ/COM PORT Conflicts'
Document ID: 1996112511055
Web URL:
http://service1.symantec.com/SUPPORT/pca.nsf/docid/1996112511055

Title: 'TROUBLESHOOTING: How To Troubleshoot TAPI Modem Problems.'
Document ID: 199719104413
Web URL:
http://service1.symantec.com/SUPPORT/pca.nsf/docid/199719104413

Title: 'Internal Modems Using IRQ 4 or IRQ 3 and a Plug and Play BIOS
With Windows 95'
Document ID: 19961217214553
Web URL:
http://service1.symantec.com/SUPPORT/pca.nsf/docid/19961217214553

Title: 'Modem Troubleshooting with pcANYWHERE32'
Document ID: 1997128132842
Web URL:
http://service1.symantec.com/SUPPORT/pca.nsf/docid/1997128132842

Title: 'How to Prevent Applications from Launching via the Windows 95
Registry'
Document ID: 1998410131349
Web URL:
http://service1.symantec.com/SUPPORT/pca.nsf/docid/1998410131349

If after implementing the information and suggestions in the above
documents you are still having this problem, please repost and we will
continue troubleshooting this issue.

Be well.

------------------------------------------
Dana Burian [Symantec Corp.]
Senior Product Support Analyst

Please continue to post your messages to the public discussion groups as Symantec does not provide support via private e-mail.

If you have difficulty getting a response, please read the following article:

http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414

For free technical support newsletters, Knowledge Base support articles, our Online Support Genie, and FAQs, visit our pcANYWHERE support page:

http://service.symantec.com/pca
------------------------------------------


Les Coates

unread,
Sep 29, 1998, 3:00:00 AM9/29/98
to
On Sun, 27 Sep 1998 09:34:04 GMT, Dana Burian (Symantec) wrote:
> On 27 Sep 1998 03:53:42 GMT, Les Coates
> Although none of the above documents was of any use, I did unearth one that I had written down during a previous browsing session on your web site.

On 9/9/98, a response to a customer with a similar problem was your
document #1998716213547. This solution worked perfectly and all is
now well with our Dell.

Please pass along my thanks to the document's author, as well as to
the analyst who remembered it and recommended it to your other
customer. (That was the only reference to that particular document
that I found in all your messages.)
-Les Coates

Larry McDowall (Symantec)

unread,
Sep 29, 1998, 3:00:00 AM9/29/98
to
Hello Les,

Thank you for letting us know that you are up and running. The
IntelliMouse software issue is only caused by the older 2.2 version.
If you have that version, we recommend upgrading to the lasted one to
permanently resolve this.

Please let us know if we can assist you with any other issues in the
future.

On 29 Sep 1998 02:14:26 GMT, Les Coates wrote:

>On 9/9/98, a response to a customer with a similar problem was your
>document #1998716213547. This solution worked perfectly and all is
>now well with our Dell.
>
>Please pass along my thanks to the document's author, as well as to
>the analyst who remembered it and recommended it to your other
>customer. (That was the only reference to that particular document
>that I found in all your messages.)

---------------------------
Larry McDowall
Symantec Online Support
Symantec Corporation

Please continue to post your messages to the public discussion groups as Symantec does not provide support via private email.

If you have difficulty getting a response, please read the following article:

Tips on Using Symantec's Online Tech Support Discussion Groups
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414

For free technical support newsletters, Knowledge Base support articles, our Online Support Genie, and FAQs, visit our technical support page:

0 new messages