Re: [ros-dev] [ros-diffs] [tkreuzer] 53399: [VMWINST] Fix amd64 build

2011-09-04 Thread Bernd Blaauw 

Op 4-9-2011 17:10, Jérôme Gardou schreef:

Le 23/08/2011 10:58, tkreu...@svn.reactos.org a écrit :
What about :
[VMWINST] Get rid of this useless relic.
I mean it's something we have to maintain, it was written for
antediluvian vmware versions, and I see no reason to have such a thing.
I may as well write an application to install specific ATI card drivers,
or intel chipset drivers...


Well you got multiple options:
* ensure the VMware installer (MSI) can run properly so people can 
install their drivers. Makes VMWINST obsolete.
* ensure ReactOS can deal with a directory containing the bare VMware 
drivers (requiring 7zip to extract them from VMware 7 ISO).

* convert the Linux opensource VMware drivers into NT ones
* update this relic tool to finally (also) work with modern VMware ISO 
contents structure.


Nice and all that people can show off Quake2, Furmark etc in 
VirtualBox..now prove the same for other virtualisation products and 
real hardware graphics cards (Nvidia and AMD/ATI for starters, Intel 
graphics if you aim at business desktops).


Demonstrate equal progress in all used/supported platforms. Show VMWINST 
is an obsolete relic by proving VMware drivers can install on trunk 
ReactOS, including the added 3D support (OpenGL only I guess, but good 
enough for now).


___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [tkreuzer] 53399: [VMWINST] Fix amd64 build

2011-09-04 Thread Jérôme Gardou 

Le 04/09/2011 17:29, Bernd Blaauw a écrit :

Op 4-9-2011 17:10, Jérôme Gardou schreef:

Le 23/08/2011 10:58, tkreu...@svn.reactos.org a écrit :
What about :
[VMWINST] Get rid of this useless relic.
I mean it's something we have to maintain, it was written for
antediluvian vmware versions, and I see no reason to have such a thing.
I may as well write an application to install specific ATI card drivers,
or intel chipset drivers...


Well you got multiple options:
* ensure the VMware installer (MSI) can run properly so people can 
install their drivers. Makes VMWINST obsolete.
* ensure ReactOS can deal with a directory containing the bare VMware 
drivers (requiring 7zip to extract them from VMware 7 ISO).

* convert the Linux opensource VMware drivers into NT ones
* update this relic tool to finally (also) work with modern VMware ISO 
contents structure.


Nice and all that people can show off Quake2, Furmark etc in 
VirtualBox..now prove the same for other virtualisation products and 
real hardware graphics cards (Nvidia and AMD/ATI for starters, Intel 
graphics if you aim at business desktops).


Demonstrate equal progress in all used/supported platforms. Show 
VMWINST is an obsolete relic by proving VMware drivers can install on 
trunk ReactOS, including the added 3D support (OpenGL only I guess, 
but good enough for now).


___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Please, stop asking us to "port opensource linux drivers into NT ones". 
And also don't answer to this sentence and try to explain us why it 
would be so good for this project.
There's no offence meant, it's just that we don't have interest into it, 
and we lack manpower anyway.


Also, Aleksey noted that he still had use of this, I won't touch it.

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [tkreuzer] 53399: [VMWINST] Fix amd64 build [NTDLL] add missing amd64 specific exports [MSVCRT*] Fix mangled c++ exports for amd64 [OLEAUT32] Add amd64 adm stub for call_meth

2011-09-04 Thread Jérôme Gardou 

Le 23/08/2011 10:58, tkreu...@svn.reactos.org a écrit :

Author: tkreuzer
Date: Tue Aug 23 08:58:15 2011
New Revision: 53399

URL: http://svn.reactos.org/svn/reactos?rev=53399&view=rev
Log:
[VMWINST] Fix amd64 build


What about :
[VMWINST] Get rid of this useless relic.
I mean it's something we have to maintain, it was written for 
antediluvian vmware versions, and I see no reason to have such a thing. 
I may as well write an application to install specific ATI card drivers, 
or intel chipset drivers...


___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [tkreuzer] 53399: [VMWINST] Fix amd64 build [NTDLL] add missing amd64 specific exports [MSVCRT*] Fix mangled c++ exports for amd64 [OLEAUT32] Add amd64 adm stub for call_meth

2011-09-04 Thread Aleksey Bragin 

What about :
[VMWINST] Get rid of this useless relic.
I mean it's something we have to maintain, it was written for
antediluvian vmware versions, and I see no reason to have such a thing.
I may as well write an application to install specific ATI card drivers,
or intel chipset drivers...


It's written for the most common testing platform of ReactOS, the 
maintaining effort spent over years was minimal, and it just does its job 
very quickly, even with VMWare 7 (provided you copy necessary video driver 
files from its CD to modules\optional when building your bootcd).


WBR,
Aleksey. 



___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [tkreuzer] 53399: [VMWINST] Fix amd64 build [NTDLL] add missing amd64 specific exports [MSVCRT*] Fix mangled c++ exports for amd64 [OLEAUT32] Add amd64 adm stub for call_meth

2011-09-04 Thread Bernd Blaauw 

Op 4-9-2011 17:24, Aleksey Bragin schreef:

It's written for the most common testing platform of ReactOS, the
maintaining effort spent over years was minimal, and it just does its
job very quickly, even with VMWare 7 (provided you copy necessary video
driver files from its CD to modules\optional when building your bootcd).


Is this documented somewhere including a howto, for 'most common testing 
platform'?
I was under the impression VMWINST was only able to handle old ISO 
structure of Vmware tools, not new tools ISO (despite me having 
explained structure before, and 7zip doing the job), nor your above 
listed method. If it actually works, good news (for vmwinst.exe in phase 
3). Having to rebuild CD instead of pointing to files on a CD or 
directory, is an annoying requirement however.



WBR,
Aleksey.


thanks for above info. Gives some hope after having messed around with 
FreeLDR all day in vain.


___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [tkreuzer] 53399: [VMWINST] Fix amd64 build [NTDLL] add missing amd64 specific exports [MSVCRT*] Fix mangled c++ exports for amd64 [OLEAUT32] Add amd64 adm stub for call_meth

2011-09-04 Thread Javier Agustìn Fernàndez Arroyo 
well i think nowadays 'most common testing platform' is VirtualBox, not sure
about VMWare.

On Sun, Sep 4, 2011 at 5:34 PM, Bernd Blaauw  wrote:

> Op 4-9-2011 17:24, Aleksey Bragin schreef:
>
>  It's written for the most common testing platform of ReactOS, the
>> maintaining effort spent over years was minimal, and it just does its
>> job very quickly, even with VMWare 7 (provided you copy necessary video
>> driver files from its CD to modules\optional when building your bootcd).
>>
>
> Is this documented somewhere including a howto, for 'most common testing
> platform'?
> I was under the impression VMWINST was only able to handle old ISO
> structure of Vmware tools, not new tools ISO (despite me having explained
> structure before, and 7zip doing the job), nor your above listed method. If
> it actually works, good news (for vmwinst.exe in phase 3). Having to rebuild
> CD instead of pointing to files on a CD or directory, is an annoying
> requirement however.
>
>  WBR,
>> Aleksey.
>>
>
> thanks for above info. Gives some hope after having messed around with
> FreeLDR all day in vain.
>
>
> __**_
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/**mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev