Re: Compatibility with Widows 10 v1809

2019-05-20 Thread Peter Adam via 4D_Tech
t;> > Sent: Monday, May 20, 2019 4:35 PM > To: Randy Engle <4d.l...@xc2.us <mailto:4d.l...@xc2.us>> > Cc: 4D iNug Technical <4d_tech@lists.4d.com <mailto:4d_tech@lists.4d.com>> > Subject: Re: Compatibility with Widows 10 v1809 > > Thanks, > >

Re: Compatibility with Widows 10 v1809

2019-05-20 Thread Peter Adam via 4D_Tech
ay 19, 2019 5:39 AM > To: 4D iNug Technical <4d_tech@lists.4d.com <mailto:4d_tech@lists.4d.com>> > Cc: Peter Adam mailto:peter.a...@me.com>> > Subject: Re: Compatibility with Widows 10 v1809 > > After extensive trouble shooting, all security functions turned o

RE: Compatibility with Widows 10 v1809

2019-05-20 Thread Randy Engle via 4D_Tech
AM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Peter Adam Subject: Re: Compatibility with Widows 10 v1809 After extensive trouble shooting, all security functions turned off, a v17R4 server will not launch. No screen is displayed nor is any background MIDI screen showing. This is ha

Re: Compatibility with Widows 10 v1809

2019-05-19 Thread Peter Adam via 4D_Tech
After extensive trouble shooting, all security functions turned off, a v17R4 server will not launch. No screen is displayed nor is any background MIDI screen showing. This is happening on a win 10 Pro v1809 box. Is anyone using this version of Win 10 with 4D v17R4? Cheers, Peter Adam Adam,

Re: Compatibility with Widows 10 v1809

2019-05-17 Thread Peter Adam via 4D_Tech
V17R4 won’t launch either. prntvpt.dll missing and a bunch of other stuff. Any help? Cheers, Peter Adam Adam, Zievert & Associates P/L e: peter.a...@me.com Skype Phone: +61 3 9016 379 t: +61 3 9836 3539 m: 0419 552 462 www.adamzievert.com.au > On 17 May 2019, at 9:06 am, Peter Adam via 4D

Compatibility with Widows 10 v1809

2019-05-16 Thread Peter Adam via 4D_Tech
I have reports of compatibility issues with windows 10 v1809. It appears that 4D is attempting to write an IP address to the CSC folder, one of windows system folders. This is when launching the 4D v13 client. v13 running on a Windows 10 v1709 client works fine. Any suggestions about what to t