|
Cyndi, I am making the *assumption* that the two PC's are Win 95 based. The update probably occurred because the CA/400 Update Function is automatically running when the PC is booted up for the first time after a PTF CUME has been applied on the AS/400. If you want to control when a PC is updated with a CA/400 service pack, remove the Update function from the Win 95 startup folder. You then control when the updates occur. How are CA/400 PTF's being installed on PC's? If you are loading PTF's via service packs retrieved from IBM via the Internet, you should remove the CA/400 Update from the Win 95 Startup folder. This will prevent AS/400 updates from occurring on the first connect after a PTF CUME has been loaded. If you are updating from the AS/400, you should do the same. I have no dependency on the AS/400 for CA/400 service packs. I get them via the Internet and keep them on an NT server. Once I have tested the service pack, I move it to a directory that can be accessed. I also have the auto update function removed from the Win 95 Start up folder. You should be able to back out a service pack via the uninstall. Just make sure that you have access to the earlier CA/400 service pack. HTH.... Mike Shaw -----Original Message----- From: Cyndi Bradberry <CyndiB@ihfa.org> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Date: Friday, July 31, 1998 3:31 PM Subject: Client Access File Transfer Problem >I have a problem with Client Access. >I am at Client Access V3R1M2 SF39220. I have the cwbtfr.ini with >the ForceTranslation=1 and I can transfer files from the AS/400 >with no problem. >On July 25th, we put on the latest cum for V3R7. >I now have two pc's (at least) that say Client Access V3R1M2 >SF41904. We have replaced the .ini file on their drives (it was >there before cum) but when they d/l a file, they still get hex >instead of ASCII. >What do I need to get them back to file translation? >TIA >Cyndi Bradberry >IHFA, Boise Idaho >+--- >| 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.