×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Thomas,
Nope. On my system, unless the IFS is mapped as a drive to the PC, I get
the DOS box with the message 'Access denied'.
I've seen this happen when the userid/password on the PC doesn't match
the userid/password on the i.
If Windows tries to access \\192.168.0.3\root\pdf\stitch.pdf and the
user/password doesn't match, it simply fails with access denied.
However, if Windows tries to access \\192.168.0.3\root (just the
computer & share name) and the userid/password doesn't match, it'll
bring up a box prompting the user for the userid/password.
If this sounds like the same scenario, you might try doing a "net use"
command prior to accessing the PDF. something like
net use \\192.168.0.3\root bigboy /USER:klemscot
This associates the userid=klemscot, password=bigboy with the
\\192.168.0.3\root share on the network. After that, when you try to
access \\192.168.0.3\root\pdf\stitch.pdf, it should work.
However... I have to tell you that I positively HATE the way Windows
Networking works. IT's too complicated. It has too many weird quirks
(like this one). If at all possible, I suggest accessing the PDF via
another prototcol, such as http. HTTP is a great protocol for this sort
of thing.
In that case, you could use
STRPCCMD PCCMD('rundll32 url,FileProtocolHandler
http://192.168.0.3/whatever/stitch.pdf')
That would work a lot better, in my experience.
midrange.com
