reactos-kernel

[ros-kernel] Bug Report - VIM for Win32

[Steven E. <Ste...@kn...>]

vim.exe crashes because it cant import GetSysColotPen which is a export of
user32. This is what happens when i try to run vim.exe for win32

Transferring control to image at 4011d4
(misc/dllmain.c:38) ADVAPI32: DllMain() done
LdrFixupForward: failed to load NTDLL
LdrGetExportByName(): failed to find GetSysColorPen
Failed to import GetSysColorPen
LdrFixupImports() failed
LdrFixupImports:failed to load comctl32.dll
LdrFixupImports() failed
LdrFixupImports:failed to load SHELL32.dll
LdrFixupImports() failed
Failed to initialize image


I've made a install script for wine so if anyone needs to test this or other
programs under reactos just go to the root or the reactos source tree and
run installwine.bat this will install the wine dlls to 
%SYSTEMROOT%\system32 and the winelib programs to C:\bin. 

Steven###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/

[ros-kernel] Re: Bug Report - VIM for Win32

[Phillip S. <ps...@cf...>]

Isn't vim console based?  Then why the heck is it importing things from 
user32, comctl32, and shell32?

At 03:40 PM 11/11/2001 -0500, you wrote:

>vim.exe crashes because it cant import GetSysColotPen which is a export of 
>user32. This is what happens when i try to run vim.exe for win32
>
>Transferring control to image at 4011d4
>(misc/dllmain.c:38) ADVAPI32: DllMain() done
>LdrFixupForward: failed to load NTDLL
>LdrGetExportByName(): failed to find GetSysColorPen
>Failed to import GetSysColorPen
>LdrFixupImports() failed
>LdrFixupImports:failed to load comctl32.dll
>LdrFixupImports() failed
>LdrFixupImports:failed to load SHELL32.dll
>LdrFixupImports() failed
>Failed to initialize image
>
>I've made a install script for wine so if anyone needs to test this or 
>other programs under reactos just go to the root or the reactos source 
>tree and run installwine.bat this will install the wine dlls to
>
>%SYSTEMROOT%\system32 and the winelib programs to C:\bin.
>
>Steven###########################################
>

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================

[ros-kernel] Re: Bug Report - VIM for Win32

[Jakob E. <ja...@vm...>]

AFAIK there are two vims for windows out there.

A unix one - compiled under cygwin.

A native windows version with a lot of windows bells and whistles.


On Sun, Nov 11, 2001 at 03:54:32PM -0500, Phillip Susi wrote:
> Isn't vim console based?  Then why the heck is it importing things from 
> user32, comctl32, and shell32?
> 
> At 03:40 PM 11/11/2001 -0500, you wrote:
> 
> >vim.exe crashes because it cant import GetSysColotPen which is a export of 
> >user32. This is what happens when i try to run vim.exe for win32
> >
> >Transferring control to image at 4011d4
> >(misc/dllmain.c:38) ADVAPI32: DllMain() done
> >LdrFixupForward: failed to load NTDLL
> >LdrGetExportByName(): failed to find GetSysColorPen
> >Failed to import GetSysColorPen
> >LdrFixupImports() failed
> >LdrFixupImports:failed to load comctl32.dll
> >LdrFixupImports() failed
> >LdrFixupImports:failed to load SHELL32.dll
> >LdrFixupImports() failed
> >Failed to initialize image
> >
> >I've made a install script for wine so if anyone needs to test this or 
> >other programs under reactos just go to the root or the reactos source 
> >tree and run installwine.bat this will install the wine dlls to
> >
> >%SYSTEMROOT%\system32 and the winelib programs to C:\bin.
> >
> >Steven###########################################
> >
> 
> ====================================================
> = To remove yourself from this mailing list, go to =
> = http://www.reactos.com/home/mailing.html         =
> ====================================================
> 

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================

[ros-kernel] Re: Bug Report - VIM for Win32

[James T. <jim...@ad...>]

Hi,
Jakob Eriksson wrote:
> 
> AFAIK there are two vims for windows out there.
> 
> A unix one - compiled under cygwin.
> 
> A native windows version with a lot of windows bells and whistles.
> 
> On Sun, Nov 11, 2001 at 03:54:32PM -0500, Phillip Susi wrote:
> > Isn't vim console based?  Then why the heck is it importing things from
> > user32, comctl32, and shell32?
> >
> > At 03:40 PM 11/11/2001 -0500, you wrote:
> >
> > >vim.exe crashes because it cant import GetSysColotPen which is a export of
> > >user32. This is what happens when i try to run vim.exe for win32

Of course! It's just a stub right now in user32!. "GetSysColorPen".

> > >
> > >Transferring control to image at 4011d4
> > >(misc/dllmain.c:38) ADVAPI32: DllMain() done
> > >LdrFixupForward: failed to load NTDLL
> > >LdrGetExportByName(): failed to find GetSysColorPen
> > >Failed to import GetSysColorPen
> > >LdrFixupImports() failed
> > >LdrFixupImports:failed to load comctl32.dll
> > >LdrFixupImports() failed
> > >LdrFixupImports:failed to load SHELL32.dll
> > >LdrFixupImports() failed
> > >Failed to initialize image
> > >
> > >I've made a install script for wine so if anyone needs to test this or
> > >other programs under reactos just go to the root or the reactos source
> > >tree and run installwine.bat this will install the wine dlls to
> > >
> > >%SYSTEMROOT%\system32 and the winelib programs to C:\bin.
> > >
> > >Steven###########################################

I'm in the process of reading a book called "Windows Graphics Programming, 
with Win32 GDI & DirectDraw". Soon I'll start implementing new functions in
user32 to get it ready.
James

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================

[ros-kernel] Re: Bug Report - VIM for Win32

[Craig B. <cr...@wa...>]

There is no fundamental difference between a console app and a GUI app.  =
The difference is mainly what the compiler inserts into your program as =
startup code.  Once running, both types of apps have FULL access to the =
Win32 API.  A console app can suddenly open up windows and dialog boxes; =
a GUI app can suddenly launch a console session.  You get the idea.

In addition to window-related functions, User32.dll also has lots of =
functions for messages, events, processes, and threads.  Vim uses =
User32.dll for FindWindow() (an attempt to get the console window =
handle, for the purpose of changing the icon (see below)), =
MsgWaitForMultipleObjects() (for interprocess message passing), and =
possibly other stuff.

Vim uses Shell32.dll for ExtractIcon() (it changes the icon of the =
console window while it is running) and possibly other stuff.

I don't know why Vim needs Comctl32.dll.  I wonder if this really was a =
console build rather than a GUI build.  When I build console Vim, it =
doesn't appear to link with Comctl32.dll.

Anyway, you *might* be able to strip Vim down enough so that it doesn't =
need these DLLs.  A lot of these features are not strictly necessary.


----- Original Message -----=20
From: "Phillip Susi" <ps...@cf...>
To: <ros...@re...>
Sent: Sunday, November 11, 2001 3:54 PM
Subject: [ros-kernel] Re: Bug Report - VIM for Win32


> Isn't vim console based?  Then why the heck is it importing things =
from=20
> user32, comctl32, and shell32?
>=20
> At 03:40 PM 11/11/2001 -0500, you wrote:
>=20
> >vim.exe crashes because it cant import GetSysColotPen which is a =
export of=20
> >user32. This is what happens when i try to run vim.exe for win32


====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================

[ros-kernel] Re: Bug Report - VIM for Win32

[KJK::Hyperion <no...@li...>]

At 13.40 12/11/2001 -0500, you wrote:
>Anyway, you *might* be able to strip Vim down enough so that it doesn't 
>need these DLLs.  A lot of these features are not strictly necessary.

I got an old Vi clone port lying around, found it in the Windows 98 
Resource Kit. It should be stripped down enough

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================