|
This is for Client Access Express, but try opening the '*.DTF' in notepad and adding this: [Properties] Convert65535=1 1 is convert, 0 is no conversion. ____________________Reply Separator____________________ Subject: Re:CCSID 65535 Translation in Client Access Transfer Request Author: "mark.stepan@merrillcorp.com" [SMTP:mark.stepan@merrillcorp.com] Date: 01/11/1900 1:20 PM Sorry Eric, that didn't appear to do the trick. [Cyndy made the same suggestion too]. The machine that this is running on is running Windows98. I put the file in \Windows\System [there were a bunch of other CWB* files there too], re-booted, but no [good] luck. I also tried it on my machine, but mine is Windows2000. The W98 system is being told to execute the TTO via RUNRMTCMD ... ('CALL "C:\Program Files\IBM\Client Access\RTOPCB.exe" ... <point to the TTO>) etc. Any other ideas??? Mark To: "\"mark.stepan@merrillcorp.com\" " <mark.stepan@merrillcorp.com>, "\"midrange-l@midrange.com\" " <midrange-l@midrange.com> cc: (bcc: Mark Stepan/STC/Merrill/US) Subject: Re:CCSID 65535 Translation in Client Access Transfer Request Create a text document called CWBTFR.INI with the lines: [Client Access Data Transfer] ForceTranslation=1; Save this file in your C:\WINNT folder and reboot. This will force the file transfer to convert CCSID 65535 files so they don't look like garbage. ____________________Reply Separator____________________ Subject: CCSID 65535 Translation in Client Access Transfer Requests Author: "mark.stepan@merrillcorp.com" [SMTP:mark.stepan@merrillcorp.com] Date: 01/10/1900 8:36 PM Can someone out there please clarify this CCSID stuff for me? Here's the situation: We have a computer that sits in the background and does nothing but file transfers between our Novell/NT servers and the 400's. We starting moving away from the DOS version of Client Access in favor of the Windows 9x/NT version. I came across a nuance that reared its head in the Windows version where the file was all in HEX on the NT server pafter a download]. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.