Win2000 no more natively supported?

Win2000 no more natively supported?

Postby Prisma » 2010-11-02 14:20

Just to get some things clear:

Have I seen right, that windows 2000 is no more natively supported by winvnc.exe? You need a special EXE for that OS?
Prisma
100
100
 
Posts: 264
Joined: 2005-10-27 15:50

Re: Win2000 no more natively supported?

Postby Rudi De Vos » 2010-11-02 14:45

Correct,

We use VS2010, the compiler does not longer support w2K.
W2k bins are the same as the xp>= bins, but compiled with
VS2008.

MS also stopped the distribution of w2K ( license violation Java), we can't
download the w2k iso from MS fro testing.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5295
Joined: 2004-04-23 10:21

Re: Win2000 no more natively supported?

Postby Prisma » 2010-11-02 14:52

Ok, does this mean taking the win2000 bins for newer systems has no cons? Or why should I take the VS2010 compiled version if the VS2008 version runs with every 2000+ system?
Prisma
100
100
 
Posts: 264
Joined: 2005-10-27 15:50

Re: Win2000 no more natively supported?

Postby Rudi De Vos » 2010-11-02 15:30

VS2010 is supposed to be faster then VS2008.
w2K bins works on xp>=

Only for X64 you should use the X64 version.
( The win32 version work, but some functions like bcdedit.exe fail)
Last edited by Rudi De Vos on 2010-11-02 15:39, edited 2 times in total.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5295
Joined: 2004-04-23 10:21

Re: Win2000 no more natively supported?

Postby Prisma » 2010-11-03 10:29

ouhh, that's hard...
ok, conclusion: If I want to distribute only one executable to my customers, I have to choose w2k32 bin. It'll work everywhere, possibly a little bit slower, possibly not, and a restart option, which isn't needed by everybody, won't work on X64 systems. So far correct?

What calls do you use to trigger bcedit? CreateProcess? API-calls? What makes the calls crashing or not working? Problems with the wow64 subsystem?

Are there any ambitions to bring back together the 3 open ends?
Prisma
100
100
 
Posts: 264
Joined: 2005-10-27 15:50

Re: Win2000 no more natively supported?

Postby Rudi De Vos » 2010-11-03 11:25

It works on X64, but the new function " reboot in safemode" doesn't work.
(1.0.9.2)

The bcdedit -> boot flag editor is X64 and can't be called from a w32 application.
Took me hours to find the reason why the system always answered me " file not found". Final is started a cmd from winvnc... and indeed, in the cmd started from a win32 application, certain exe does not exist.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5295
Joined: 2004-04-23 10:21

Re: Win2000 no more natively supported?

Postby Prisma » 2010-11-03 12:10

yeah, it's because you're redirected from system32 to sysWOW64. And there's no bcdedit.exe. But I got a easy workaround for you:

Before you execute bcdedit.exe just execute from the win32winvnc:

mklink c:\Windows\SysWOW64\bcdedit.exe C:\Windows\System32\bcdedit.exe

After that, your call for bcdedit.exe will be successful. It works, I've tested it.

You should have elevated rights, so it's no problem to create the link in sysWOW64.
Prisma
100
100
 
Posts: 264
Joined: 2005-10-27 15:50

Re: Win2000 no more natively supported?

Postby Rudi De Vos » 2010-11-03 13:24

Only problem is that insite winvnc w32
c:\windows\system32\bcdedit.exe
does not exist.
system32 is redirected to sysWOW64 and the real system32 is hidden.


The link need to be done in X64 mode :(
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5295
Joined: 2004-04-23 10:21

Re: Win2000 no more natively supported?

Postby Prisma » 2010-11-03 14:03

no, sorry rudi, that's not my experience. The targets path seems to be not redirected if you use mklink. I tried it myself. I let a win32app open a command shell, proofed that it is cmd32 with taskman, executed mklink, executed bcdedit.exe, works.

Give it a try...
Prisma
100
100
 
Posts: 264
Joined: 2005-10-27 15:50


Return to 1.0.9.1 (stable)

Who is online

Users browsing this forum: No registered users and 1 guest