Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #10700 > unrolled thread

VO 2.8 SP3 and Windows 10 Creators update

Started byRainer Borchmann <rainer@borchmann.de>
First post2017-06-19 11:26 -0700
Last post2017-06-25 16:08 -0700
Articles 16 — 6 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  VO 2.8 SP3 and Windows 10 Creators update Rainer Borchmann <rainer@borchmann.de> - 2017-06-19 11:26 -0700
    Re: VO 2.8 SP3 and Windows 10 Creators update "Urs Eggmann" <Urs.Eggmann@shinternet.ch> - 2017-06-19 22:35 +0200
    Re: VO 2.8 SP3 and Windows 10 Creators update "Wolfgang Riedmann" <wriedmann@gmail.com> - 2017-06-20 05:54 +0200
    Re: VO 2.8 SP3 and Windows 10 Creators update Franz Rachbauer <office@rachbauer.org> - 2017-06-20 12:08 +0200
      Re: VO 2.8 SP3 and Windows 10 Creators update James Martin <james@northwoodlumber.com> - 2017-06-20 07:58 -0400
        Re: VO 2.8 SP3 and Windows 10 Creators update Franz Rachbauer <office@rachbauer.org> - 2017-06-20 15:20 +0200
          Re: VO 2.8 SP3 and Windows 10 Creators update Franz Rachbauer <office@rachbauer.org> - 2017-06-20 19:00 +0200
            Re: VO 2.8 SP3 and Windows 10 Creators update D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-06-21 00:54 +0200
              Re: VO 2.8 SP3 and Windows 10 Creators update Franz Rachbauer <office@rachbauer.org> - 2017-06-21 06:47 +0200
                Re: VO 2.8 SP3 and Windows 10 Creators update D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-06-22 00:03 +0200
      Re: VO 2.8 SP3 and Windows 10 Creators update D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-06-27 13:59 +0200
        Re: VO 2.8 SP3 and Windows 10 Creators update D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-06-28 23:32 +0200
          Re: VO 2.8 SP3 and Windows 10 Creators update D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-06-29 23:10 +0200
            Re: VO 2.8 SP3 and Windows 10 Creators update "Wolfgang Riedmann" <wriedmann@gmail.com> - 2017-06-30 08:25 +0200
              Re: VO 2.8 SP3 and Windows 10 Creators update D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-06-30 20:37 +0200
    Re: VO 2.8 SP3 and Windows 10 Creators update Rainer Borchmann <rainer@borchmann.de> - 2017-06-25 16:08 -0700

#10700 — VO 2.8 SP3 and Windows 10 Creators update

FromRainer Borchmann <rainer@borchmann.de>
Date2017-06-19 11:26 -0700
SubjectVO 2.8 SP3 and Windows 10 Creators update
Message-ID<b5943e70-6a6a-464c-92d0-ef8b6f0e035b@googlegroups.com>
Hello Community,
i have to reopen an older VO2.8SP3 Projekt 
on a Windows 10 Creators Update (Version 1703 Build 15063.413).
did this combination will run seriosly fine?
If you recomend a older windows version... I have an XPSP3 machine
running (for astrophysical mathematics and teleskope control).
Is that in this case OK to run vo2.8?
I have no exotic addons in this project, except RP2.x.

thanks for any help.

Rainer Borchmann 

[toc] | [next] | [standalone]


#10701

From"Urs Eggmann" <Urs.Eggmann@shinternet.ch>
Date2017-06-19 22:35 +0200
Message-ID<eqqrhdFm72sU1@mid.individual.net>
In reply to#10700
Hi Rainer,
Nice to hear you again....

Just for the worste case with W10:
I'm running also VO 2.84b on a XP machine. Works still OK. RP2 I do not 
know.
Best regard from the Rhine Falls
Urs

"Rainer Borchmann" <rainer@borchmann.de> schrieb im Newsbeitrag 
news:b5943e70-6a6a-464c-92d0-ef8b6f0e035b@googlegroups.com...
> Hello Community,
> i have to reopen an older VO2.8SP3 Projekt
> on a Windows 10 Creators Update (Version 1703 Build 15063.413).
> did this combination will run seriosly fine?
> If you recomend a older windows version... I have an XPSP3 machine
> running (for astrophysical mathematics and teleskope control).
> Is that in this case OK to run vo2.8?
> I have no exotic addons in this project, except RP2.x.
>
> thanks for any help.
>
> Rainer Borchmann 

[toc] | [prev] | [next] | [standalone]


#10703

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2017-06-20 05:54 +0200
Message-ID<eqrkjmFrdjlU1@mid.individual.net>
In reply to#10700
Hi Rainer,

I don't know about SP3, but we are using SP4 without any issue on
Creators Update machines. I don't see any issue also for SP3.

Wolfgang

Rainer Borchmann wrote:

> Hello Community,
> i have to reopen an older VO2.8SP3 Projekt 
> on a Windows 10 Creators Update (Version 1703 Build 15063.413).
> did this combination will run seriosly fine?
> If you recomend a older windows version... I have an XPSP3 machine
> running (for astrophysical mathematics and teleskope control).
> Is that in this case OK to run vo2.8?
> I have no exotic addons in this project, except RP2.x.
> 
> thanks for any help.
> 
> Rainer Borchmann 



-- 

[toc] | [prev] | [next] | [standalone]


#10705

FromFranz Rachbauer <office@rachbauer.org>
Date2017-06-20 12:08 +0200
Message-ID<oias6n$1cce$1@gioia.aioe.org>
In reply to#10700
Hi there,
one of my customers actually has a W10 machine with EXE compiled with VO 
2.8 SP4 and RP 2.17, which denies to print using RpPrinter since last 
night creators update. Printer are OK, printing from other progs no problem.

oPrinter := RpPrinter{oWindow, SELF}
IF oPrinter:IsValid    // => FALSE

It looks like something blocks RP Dlls! Any idea where to search or what 
to do? No recovery point before creators update made by W10, so no 
recovery possible.

Regards, Franz


Am 19.06.2017 um 20:26 schrieb Rainer Borchmann:
> Hello Community,
> i have to reopen an older VO2.8SP3 Projekt
> on a Windows 10 Creators Update (Version 1703 Build 15063.413).
> did this combination will run seriosly fine?
> If you recomend a older windows version... I have an XPSP3 machine
> running (for astrophysical mathematics and teleskope control).
> Is that in this case OK to run vo2.8?
> I have no exotic addons in this project, except RP2.x.
>
> thanks for any help.
>
> Rainer Borchmann
>

[toc] | [prev] | [next] | [standalone]


#10706

FromJames Martin <james@northwoodlumber.com>
Date2017-06-20 07:58 -0400
Message-ID<oib2e5$gf9$1@dont-email.me>
In reply to#10705
Can you run in compatibility mode?

James

On 2017-06-20 06:08 AM, Franz Rachbauer wrote:
> Hi there,
> one of my customers actually has a W10 machine with EXE compiled with VO 
> 2.8 SP4 and RP 2.17, which denies to print using RpPrinter since last 
> night creators update. Printer are OK, printing from other progs no 
> problem.
> 
> oPrinter := RpPrinter{oWindow, SELF}
> IF oPrinter:IsValid    // => FALSE
> 
> It looks like something blocks RP Dlls! Any idea where to search or what 
> to do? No recovery point before creators update made by W10, so no 
> recovery possible.
> 
> Regards, Franz
> 
> 
> Am 19.06.2017 um 20:26 schrieb Rainer Borchmann:
>> Hello Community,
>> i have to reopen an older VO2.8SP3 Projekt
>> on a Windows 10 Creators Update (Version 1703 Build 15063.413).
>> did this combination will run seriosly fine?
>> If you recomend a older windows version... I have an XPSP3 machine
>> running (for astrophysical mathematics and teleskope control).
>> Is that in this case OK to run vo2.8?
>> I have no exotic addons in this project, except RP2.x.
>>
>> thanks for any help.
>>
>> Rainer Borchmann
>>
> 

[toc] | [prev] | [next] | [standalone]


#10707

FromFranz Rachbauer <office@rachbauer.org>
Date2017-06-20 15:20 +0200
Message-ID<oib7fa$1vmf$1@gioia.aioe.org>
In reply to#10706
Hi James,
Application EXE in compatibility mode for W7 or XP - no change, problem 
exists!

Regards, Franz

Am 20.06.2017 um 13:58 schrieb James Martin:
> Can you run in compatibility mode?
>
> James
>
> On 2017-06-20 06:08 AM, Franz Rachbauer wrote:
>> Hi there,
>> one of my customers actually has a W10 machine with EXE compiled with
>> VO 2.8 SP4 and RP 2.17, which denies to print using RpPrinter since
>> last night creators update. Printer are OK, printing from other progs
>> no problem.
>>
>> oPrinter := RpPrinter{oWindow, SELF}
>> IF oPrinter:IsValid    // => FALSE
>>
>> It looks like something blocks RP Dlls! Any idea where to search or
>> what to do? No recovery point before creators update made by W10, so
>> no recovery possible.
>>
>> Regards, Franz
>>
>>
>> Am 19.06.2017 um 20:26 schrieb Rainer Borchmann:
>>> Hello Community,
>>> i have to reopen an older VO2.8SP3 Projekt
>>> on a Windows 10 Creators Update (Version 1703 Build 15063.413).
>>> did this combination will run seriosly fine?
>>> If you recomend a older windows version... I have an XPSP3 machine
>>> running (for astrophysical mathematics and teleskope control).
>>> Is that in this case OK to run vo2.8?
>>> I have no exotic addons in this project, except RP2.x.
>>>
>>> thanks for any help.
>>>
>>> Rainer Borchmann
>>>
>>

[toc] | [prev] | [next] | [standalone]


#10708

FromFranz Rachbauer <office@rachbauer.org>
Date2017-06-20 19:00 +0200
Message-ID<oibkbh$oc5$1@gioia.aioe.org>
In reply to#10707
Problem solved!
RpPrinter looks in WIN.INI for standard printer at Init(). Creators 
update has killed this printer, so no standard printer was available 
anymore. Thus RpPrinter comes back with FALSE at Init().

Thanks to all!
Franz

[toc] | [prev] | [next] | [standalone]


#10710

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2017-06-21 00:54 +0200
Message-ID<569jkcle40htl4dkljchorvdoejc9grggi@4ax.com>
In reply to#10708
Replying on message of Tue, 20 Jun 2017 19:00:23 +0200 from Franz
Rachbauer:


 Hello Franz,

>Problem solved!
>RpPrinter looks in WIN.INI for standard printer at Init(). Creators 
>update has killed this printer, so no standard printer was available 
>anymore. Thus RpPrinter comes back with FALSE at Init().
>
Ah! The usual suspect for Report Pro problems.

I don't expect big VO (program) problems with the Creator's Update.
Nevertheless I recommend everyone to go to Settings, Updates, Advanced
Options, Defer feature Updates.

This will postpone updates like the Creator update for at least 4
months. I wish I had done the same with the Anniversary Update which
would have saved me a few 100's unnecessary clicks to close the lock
screen. The only thing I thought could be useful was Windows Ink
Workspace to create screen grabs with arrows etc, but the fact that
you have to close that app before you have access to anything else in
your screen alo made this new feature a disappointment and I hardly
ever use it - the Snipping Tool is easier..

I haven't found anything useful in the Creators update and no doubt
there's something nasty in it like the obligatory lockscreen in the
previous version.

I do not regret having gone to W10 but I would prefer to skip all the
feature updates. Just like I skipped trash like Windows Vista or
Window ME in the past.

Dick

[toc] | [prev] | [next] | [standalone]


#10712

FromFranz Rachbauer <office@rachbauer.org>
Date2017-06-21 06:47 +0200
Message-ID<oictpu$hr5$1@gioia.aioe.org>
In reply to#10710
Hi Dick,

Am 21.06.2017 um 00:54 schrieb D.J.W. van Kooten:
> Replying on message of Tue, 20 Jun 2017 19:00:23 +0200 from Franz
> Rachbauer:
>
>
>  Hello Franz,
>
>> Problem solved!
>> RpPrinter looks in WIN.INI for standard printer at Init(). Creators
>> update has killed this printer, so no standard printer was available
>> anymore. Thus RpPrinter comes back with FALSE at Init().
>>
> Ah! The usual suspect for Report Pro problems.
>
> I don't expect big VO (program) problems with the Creator's Update.
> Nevertheless I recommend everyone to go to Settings, Updates, Advanced
> Options, Defer feature Updates.
>
> This will postpone updates like the Creator update for at least 4
> months.

So you hope that other users run into troubles with these updates and 
someone has posted a solution meanwhile <g>. But what when all users 
suspend these updates for at least 4 months?

Regards, Franz

I wish I had done the same with the Anniversary Update which
> would have saved me a few 100's unnecessary clicks to close the lock
> screen. The only thing I thought could be useful was Windows Ink
> Workspace to create screen grabs with arrows etc, but the fact that
> you have to close that app before you have access to anything else in
> your screen alo made this new feature a disappointment and I hardly
> ever use it - the Snipping Tool is easier..
>
> I haven't found anything useful in the Creators update and no doubt
> there's something nasty in it like the obligatory lockscreen in the
> previous version.
>
> I do not regret having gone to W10 but I would prefer to skip all the
> feature updates. Just like I skipped trash like Windows Vista or
> Window ME in the past.
>
> Dick
>

[toc] | [prev] | [next] | [standalone]


#10717

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2017-06-22 00:03 +0200
Message-ID<lqqlkc1ns1dp8c7ui835otp3jpt3g3tftl@4ax.com>
In reply to#10712
Replying on message of Wed, 21 Jun 2017 06:47:46 +0200 from Franz
Rachbauer:


 Hello Franz,

>So you hope that other users run into troubles with these updates and 
>someone has posted a solution meanwhile <g>. But what when all users 
>suspend these updates for at least 4 months?
>

<g>.

But seriously, that is exactly what Microsoft intends to happen.

https://technet.microsoft.com/en-us/windows/release-info.aspx

The Current Branch for Business (CBB) is 1607 (of 29-11-2016) and this
"status" is only assigned after the home users have beta tested it.
See
https://www.howtogeek.com/223083/what-does-%E2%80%9Cdefer-upgrades%E2%80%9D-in-windows-10-mean/
"Why defer updates".

Home users can not defer updates unless they disable the Windows
update service; which btw works very well. 

Dick

[toc] | [prev] | [next] | [standalone]


#10729

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2017-06-27 13:59 +0200
Message-ID<iih4lc56apf2ki1vikua09887b34jeimhk@4ax.com>
In reply to#10705
Replying on message of Tue, 20 Jun 2017 12:08:13 +0200 from Franz
Rachbauer:


 Hello Franz,

>Hi there,
>one of my customers actually has a W10 machine with EXE compiled with VO 
>2.8 SP4 and RP 2.17, which denies to print using RpPrinter since last 
>night creators update. Printer are OK, printing from other progs no problem.
>
>oPrinter := RpPrinter{oWindow, SELF}
>IF oPrinter:IsValid    // => FALSE
>

In the end I couldn't resist and installed the Creators Update, about
6 weeks earlier than the defer date. Apart from the usual problems
with Windows Updates (one PC where it didn't work, re-installing the
W7 games which every major updates blundly removes, telling with every
single type of file opened for the first time "no I still don't want
this opened with something from Microsoft") it seems to work about the
same as the previous version. No unpleasant surprises yet and the
option to make folders (in some ackward way) in the W10 menu would
almost make it usable as it's slowly getting into the direction what
the Class Windows did and does. Still I don't think there's anything
in it really worth the update but it doesn't really seem to harm my
system either.

To be sure if no other problems existed I tried the Report Pro print
from my program (created with VO 28. SP4 & Report Pro 2.16k) and this
created a printjob for my printer as I expected without problems.


@Rainer:

>I decided to run VO2.8 on a virtual XP Machine.

I wouldn't do that if I were you. I expect none of your clients still
use XP and many will use W10. You better see any problems (if any...)
first, before your clients do.

Dick

[toc] | [prev] | [next] | [standalone]


#10736

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2017-06-28 23:32 +0200
Message-ID<dp78lcta9tlbvnvfjvtvbp5ce28kuev6c3@4ax.com>
In reply to#10729
Replying on message of Tue, 27 Jun 2017 13:59:28 +0200 from D.J.W. van
Kooten:


>but it doesn't really seem to harm my system either.

Soon I discovered that it did.

Currently Windows Search doesn't work anymore; if tried manually it
gives Error 3 The system can not find the file specified.

Worse is that I can't create appx packages anymore using the
DesktopAppConverter. This worked perfectly before my update. 

A Microsoft Engineer created it from me and then I couldn't install it
while it worked on my laptop where the update fortunately failed.
Tomorrow I am going to roll back the update and again I repeat my
advise to defer W10 updates as long as you can.

Dick

[toc] | [prev] | [next] | [standalone]


#10743

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2017-06-29 23:10 +0200
Message-ID<mlqalcp4je56o3nqeu35n8925fgol7smg2@4ax.com>
In reply to#10736
Replying on message of Wed, 28 Jun 2017 23:32:24 +0200 from D.J.W. van
Kooten:


>Tomorrow I am going to roll back the update and again I repeat my
>advise to defer W10 updates as long as you can.
>

The roll back worked pretty well. I lost some shortcuts in my Classic
Shell menu (where they show empty) which also mean they can not be
found in the W10 menu, but restoring them by mostly copying from
another PC made them available in both menu's again.

And everything is working again as it did (and should).

No idea why an upgrade "by the book" (using Windows10UpgraderApp.exe),
over 2 months after it's first appearance, can mess up things so much.
I hope I can defer this "feature update" for a year (which is possible
for feature updates after the Creators Update).

Dick

[toc] | [prev] | [next] | [standalone]


#10744

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2017-06-30 08:25 +0200
Message-ID<erm96sF3028U1@mid.individual.net>
In reply to#10743
Hi Dick,

> > Tomorrow I am going to roll back the update and again I repeat my
> > advise to defer W10 updates as long as you can.
> > 
> 
> The roll back worked pretty well. I lost some shortcuts in my Classic
> Shell menu (where they show empty) which also mean they can not be
> found in the W10 menu, but restoring them by mostly copying from
> another PC made them available in both menu's again.

the Classic Shell Menu can cause issues with Windows 10 upgrades as it
is a system component. Normally you should uninstall it before and
reinstall it afterwards.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#10745

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2017-06-30 20:37 +0200
Message-ID<pn3dlctolqdfkjd64s8h11tmjmu819g0je@4ax.com>
In reply to#10744
Replying on message of Fri, 30 Jun 2017 08:25:31 +0200 from Wolfgang
Riedmann:


 Hello Wolfgang,

>the Classic Shell Menu can cause issues with Windows 10 upgrades as it
>is a system component. Normally you should uninstall it before and
>reinstall it afterwards.
>
Ok, good to know. With earlier W10 updates I never had trouble except
that the Windows 7 games are always deinstalled, but I can easily
reinstall them.

I decided to create a W10 start menu with the programs I use 90% of
the time and use that for a while and keep my Classic Start menu for
the much quicker browsing and for anything which does not work in the
W10 menu.

It is quite remarkable that you can only see those apps in that W10
menu which are present in the 2 paths associated with the classic
startmenu. But you can not add anything in the W10 menu which is not
there, while in the Classic Start menu you can just restore or create
shortcut links. Only from then these can be chosen from the W10 menu
as well. Several type of links simply do not work in the W10 menu.
E.g. I have 2 shortcuts to Agent (X#/Vulcan and this ng), with a
different directory. I can use these from the desktop and from the
Classic Shell Menu. But as soon as I pin one of them to start (as they
are visible after I dragged them to the classic shell menu) and try
the next, the previous will be overwritten.

Even if I would want to use the W10 menu only, this proves that it can
not work without the Classic Shell menu.

Dick

[toc] | [prev] | [next] | [standalone]


#10724

FromRainer Borchmann <rainer@borchmann.de>
Date2017-06-25 16:08 -0700
Message-ID<2af5a8b9-2f26-45c7-886c-a27637cb6966@googlegroups.com>
In reply to#10700
Hello Community,
thanks for all this helping hints.
I decided to run VO2.8 on a virtual XP Machine.
But i hope to find solution/workaround for printing from
a W10 Computer in the next weeks.

Thank you all

Rainer

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web