It's called outlook WEB access - come on Microsoft let us worry about the web browser not the OS. I'm still hoping someone will find a solution for this. I quoted them a new workstation and a KVM switch, with the hopes that the AS400 team will work on porting that print configuration. I finally setup IMAP in Thunderbird, but none of the authentication methods would allow for SMTP. After wasting two hours trying to get OWA to run with ?path=/classic, or Lite mode, on several browsers, with IETab, with oldversions, even trying emClient which requires a Universal C Runtime that wasn't available on XP. The AS400 support service refuses to attempt making this print job work on a modern OS, even though we've proven the iSeries emulation works on Windows 10. As an MSP I can only give my best recommendations, doesn't mean they'll follow them.Ī manufacturing company still uses iSeries on XP to connect to AS400, and print work orders to a Kyocera. I share your pain sir, ran into this last night. We still have an xray system that the software was hard coded to work with at most windows 2000 and could only work with 3 models of cards which of course none were available when the PC PSU decided to die and fry all of the PCI (I think) cards to they are left with live analog display only with a BNC connector, this also had some weird media converters that converted it to firewire then back to an NTSC signal. They couldn't even be upgraded to later version of DOS.Ĭan't beat good old DOS, we had one piece of equipment that ran on a serial cable that we managed to get running with DOSbox emulator on Windows 10, last year that piece of equipment finally died and there were only 2 people in the world we could find that are able to service them and recalibrate the software and both are past retirement. In the role I just left which was another manufacturing company I had to support 2 devices that still ran on dos 5.0. I'm lucky in this job I only have a couple of machines that run on XP. On a side note, I still have to support some machines that only transfer data over a serial cable (DB-9 to DB-25 connectors with custom pinouts) and these machines are the kind with a CRT Green/Black style screen and even have Windows 95 running a DOS program for spectrographic analysis of metal composition. I still have to support some W2K and WXP machines for this reason, the hardware was state of the art when it was built but these machines have a life expectancy that is far greater than any OS so we have a "Embedded Controls" VLAN which can only contact a single server to pull out CNC programs, for anything beyond that a modern workstation is required as mentioned by most others. Having seen all the descriptions I expect the OP is in a situation much like me with having to support old gear as manufacturers won't upgrade the OS for integrated controls as the drivers for stuff like control/interface cards for CNC will not be compatible with an OS beyond that in which they were written so I understand the pain the OP must be in having to support. The whole system is pretty seemless.Ībout the only things that will not work are OLE integrations and lets face it those never worked right even back with XP was the norm. This would let you connect to your Office 365 using Modern Auth in a Windows 10 native application and pass clipboard or file data to a file share and pick it up in the legacy application. If you need to pass information back and forth then setup shares and use something like RemoteApp. If you have a legacy application that needs to run in XP then the ideal methodology would be to install Hypver-V role on a Windows 10 system, install XP on that system as a virtual machine, put your application in the XP VM and then connect to that application via RDP. Connecting to the internet being one of those things. If you need to use XP still then I would highly suggest minimizing what you do on that system in any way. The user can't connect via IE 8 either to. I can log the user into without any issues and when I try to launch Outlook from their I get the same issue. It has been connecting to OWA without any issues for years, but this morning when the user clicks on the shortcut to point to OWA it opens with a white screen with just an image of a message file opening. I am forced to run a windows XP box to connect to and control some production machines that cost 300K to upgrade and replace, so that's out of the question currently. OK before all the comments about running XP still, I need help with an issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |