× 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.



Thanks Rob, Scott and Mark!

Unfortunately I'm just here one day a week for fill in as sys admin until the 
client completes their migration off the AS/400 & onto Oracle on System p. So 
no major new development efforts.

The only possibilities seem to be the distribution directory and WinDoze patch 
levels. The naming is 8.3 and the case matches. I'll do some digging there.

Thanks again!

Kendall Kinnear
Consulting System i5 Architect
Stonebridge

Cell: 214.676.3146
Fax: 972.455.7260

kendall.kinnear@xxxxxxxx
http://www.sbti.com

Sent from Windows Mobile 5

-----Original Message-----
From: "rob@xxxxxxxxx" <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: 8/1/06 1:44 PM
Subject: RE: Replacing a file to QDLS

WRKDIRE for one.
8.3 for another.  Meaning, the file has to follow an 8.3 naming 
convention.

Sample good file names:
myfile.txt
xxxxxxxx.yyy
eeeee.ff

Bad file names:
New Text Document.txt
Copy of myfile.txt
OurTest.LongExtension

And if you right click in a folder in MS explorer and select New - Text 
file, you get New Text Document.txt.  Doing that in a drive assigned to 
QDLS hurls.
If you copy myfile.txt and try to paste that in MS explorer you get Copy 
of myfile.txt.  Doing that in a drive assigned to QDLS also hurls.

Repeat after me:  "QDLS sucks"

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.