Re: Can't update IFS anymore

[rob@xxxxxxxxx]

This new share wouldn't be under QDLS would it?  Seems that Windows likes 
to create new copies with names like "Copy of otherfile.exe" or some such 
thing.  QDLS is very strict on the 8.3 naming format.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/27/2003 03:57 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Can't update IFS anymore


Anybody run into this?

For some time now, I haven't been able to update the IFS from one of my
machines.  It coincided roughly with upgrading to the last beta release of
WDSC, but I'm unable to state with certainty that that's the problem.

I have three machines, all running W2KPro, two with current updates and 
one
pretty severely out of date (its registry is so messed up that the Windows
Update fails).

In any event, two of the machines (one of them the out of date one) can 
map
a network drive to the AS/400 just fine.  One can map a drive, but this 
map
provides only READ access.  I can open a file, copy it from the IFS to my
local drive, and so on, but I cannot write to the IFS nor can I create a
file there.

The machine that is failing USED to work.  But now every time I try to do 
a
copy I get the message "Can not copy FILENAME: Access denied.  The source
file may be in use."  This happens whenever I try to copy from the PC to 
the
IFS, or from the IFS to the IFS.

Explorer also acts strangely.  If I bring up explorer and the click on the
drive to expand it, I see a list of all the folders.  But if I try to
further go in and expand one of those folders, Explorer hangs and must
actually be terminated.

And the REALLY bizarre bit to this is that I have two shares on the 
failing
machine that DO work.  Actually, three.  Two to the AS/400 in question, 
and
one to another workstation.  These were all defined a long time ago, and
continue to work just fine.  But this new share just won't work.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.