Hello, The network administrators for the school I work for have recent left and also left the network in a rather large mess. There are files such as pictures being stored in random folders on random computers all around the network leaving valuable data vulnerable. I'm hoping to move over from the older windows system to a new linux based thin client configuration with ltsp. So far I am using SUSE 9.1 to test and everything runs great as far as this is concerned. The problem runs in that the school requires a certain piece of software that they use to manage their business processes (attendance, billing, etc). I've been playing with WINE and have come very close to getting the system to work. The software has been running on a Windows 95 computer quite well and so I copied over the application directory and then through a lot of trial and error I settled on what I believe to be the right DLLs that were necessary from the Windows\System32 directory from one of our Windows 95 computers. The native DLLs that I'm trying to use are: msvbvm60.dll, oleaut32.dll, msvcrt20.dll, rpcrt4.dll, netapi.dll, netbios.dll, oleaut32.dll, rpcrt4.dll, ole32.dll, netapi32.dll, msvcrt20.dll. The wine version is 20040213 and was included with my distribution. This is an error I get when running the notepad that is included with wine. Notepad will start and seems to run perfectly though. This is what I get from having all of the above files in the folder: suse:~/.wine/fake_windows/ProCare # wine PRO32.exe Could not stat /media/floppy (No such file or directory), ignoring drive A: Could not stat /media/cdrom (No such file or directory), ignoring drive M: err:seh:setup_exception stack overflow 96 bytes in thread 0015 eip 40076a15 esp 40590fa0 stack 0x40590000-0x40690000 suse:~/.wine/fake_windows/ProCare # If I remove the netapi.dll, the netbios.dll, and the netapi32.dll files I will get this: suse:~/.wine/fake_windows/ProCare # rm NET NETAPI.DLL NETAPI32.DLL NETBIOS.DLL suse:~/.wine/fake_windows/ProCare # rm NET* -f suse:~/.wine/fake_windows/ProCare # ls . BAKPR.INI MSVBVM60.DLL PRO32.EXE PROPR.INI PRO_PR32.EXE RDini index.html.1 .. CHECK32.EXE MSVCRT20.DLL PROAP.INI PRO_AP32.EXE PocketPC REPAIR32.EXE msvcrt.dll BAKAP.INI Help OLE32.DLL PROAR.INI PRO_AR32.EXE ProCare.INI RPCRT4.DLL BAKAR.INI Install OLEAUT32.DLL PROCBT32.EXE PRO_IR32.EXE ProCare.INI~ VISDATA.EXE suse:~/.wine/fake_windows/ProCare # wine PRO32.exe Could not stat /media/floppy (No such file or directory), ignoring drive A: Could not stat /media/cdrom (No such file or directory), ignoring drive M: fixme:file:DeviceIoControl Unimplemented control 256 for VxD device NWLINK suse:~/.wine/fake_windows/ProCare #
This seems like some configuration errors. May I suggest as a start using the latest version of wine via the SuSE RPMs on the winehq downloads page? They should install pretty painlessly. I also know that work was done on the builtin wine versions of the DLLs you're using. Also, if you do get things working, I'd really like to talk with you more to write up a success story for the website. Heck, I'd even be willing to talk with you on the phone a bit. The prospect of Wine lowering costs of education really delights me. Thanks, Scott Ritchie Self-appointed Wine evangelist, lobbyist, and politician On Fri, 2004-12-31 at 02:13 -0800, Mitchel Constantin wrote:> Hello, > > The network administrators for the school I work for have recent left > and also left the network in a rather large mess. There are files such > as pictures being stored in random folders on random computers all > around the network leaving valuable data vulnerable. I'm hoping to > move over from the older windows system to a new linux based thin > client configuration with ltsp. So far I am using SUSE 9.1 to test and > everything runs great as far as this is concerned. > > The problem runs in that the school requires a certain piece of > software that they use to manage their business processes (attendance, > billing, etc). I've been playing with WINE and have come very close to > getting the system to work. The software has been running on a Windows > 95 computer quite well and so I copied over the application directory > and then through a lot of trial and error I settled on what I believe > to be the right DLLs that were necessary from the Windows\System32 > directory from one of our Windows 95 computers. > > The native DLLs that I'm trying to use are: msvbvm60.dll, > oleaut32.dll, msvcrt20.dll, rpcrt4.dll, netapi.dll, netbios.dll, > oleaut32.dll, rpcrt4.dll, ole32.dll, netapi32.dll, msvcrt20.dll. The > wine version is 20040213 and was included with my distribution. > > This is an error I get when running the notepad that is included with > wine. Notepad will start and seems to run perfectly though. > > This is what I get from having all of the above files in the folder: > suse:~/.wine/fake_windows/ProCare # wine PRO32.exe > Could not stat /media/floppy (No such file or directory), ignoring drive A: > Could not stat /media/cdrom (No such file or directory), ignoring drive M: > err:seh:setup_exception stack overflow 96 bytes in thread 0015 eip > 40076a15 esp 40590fa0 stack 0x40590000-0x40690000 > suse:~/.wine/fake_windows/ProCare # > > If I remove the netapi.dll, the netbios.dll, and the netapi32.dll > files I will get this: > suse:~/.wine/fake_windows/ProCare # rm NET > NETAPI.DLL NETAPI32.DLL NETBIOS.DLL > suse:~/.wine/fake_windows/ProCare # rm NET* -f > suse:~/.wine/fake_windows/ProCare # ls > . BAKPR.INI MSVBVM60.DLL PRO32.EXE PROPR.INI > PRO_PR32.EXE RDini index.html.1 > .. CHECK32.EXE MSVCRT20.DLL PROAP.INI PRO_AP32.EXE > PocketPC REPAIR32.EXE msvcrt.dll > BAKAP.INI Help OLE32.DLL PROAR.INI PRO_AR32.EXE > ProCare.INI RPCRT4.DLL > BAKAR.INI Install OLEAUT32.DLL PROCBT32.EXE PRO_IR32.EXE > ProCare.INI~ VISDATA.EXE > suse:~/.wine/fake_windows/ProCare # wine PRO32.exe > Could not stat /media/floppy (No such file or directory), ignoring drive A: > Could not stat /media/cdrom (No such file or directory), ignoring drive M: > fixme:file:DeviceIoControl Unimplemented control 256 for VxD device NWLINK > suse:~/.wine/fake_windows/ProCare # > > From some extensive google searches on this topic I came to the > understanding that the NWLINK requirement seems to be some soft of > driver (nwlink.vxd). Perhaps it seems from Novell, their Netware or > Netmonitor client(I'm guessing?). The software I'm using is extremely > straight forward and was written in Visual Basic, it uses an access > database backend and thats about it. It needs absolutely nothing > special and for sure no network access. Is there some way to bypass > this? > > Last is my configuration for the dlls in wine: > [DllOverrides] > ; some dlls you may want to change > "ntdll" = "builtin" > "oleaut32" = "builtin, native" > "ole32" = "native" > "comdlg32" = "builtin, native" > "shell32" = "builtin, native" > "shfolder" = "builtin, native" > "shlwapi" = "native, builtin" > "shdocvw" = "builtin, native" > "system" = "builtin" > "advapi32" = "native" > "msvcrt" = "native, builtin" > "mciavi.drv" = "native, builtin" > "mcianim.drv" = "native, builtin" > "msi" = "native, builtin" > "gdi" = "builtin" > "gdi32" = "builtin" > "user" = "builtin" > "user32" = "builtin" > "*" = "builtin, native" > > > Hopefully I included everything necessary. This solution with WINE > will really save the school I work for a LOT of money in upgrading and > administration costs!!! Please, any and all help will be appreciated. > > Thank you, > Mitchel > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users
On Fri, 31 Dec 2004 02:13:17 -0800, Mitchel Constantin wrote:> The native DLLs that I'm trying to use are: msvbvm60.dll, > oleaut32.dll, msvcrt20.dll, rpcrt4.dll, netapi.dll, netbios.dll, > oleaut32.dll, rpcrt4.dll, ole32.dll, netapi32.dll, msvcrt20.dll. The > wine version is 20040213 and was included with my distribution.Hi. Firstly this version is far too old. Please upgrade to a later version (doesn't have to be the very latest) and try again. Secondly, I don't know what kind of school this is, but if you can't get the app running yourself you could talk to CodeWeavers, and we may be able to fix you up (for a price, I'm afraid ...) Thirdly, you are correct about NWLINK being a driver. It's one Wine does not implement. Here are the native DLLs you are trying to use, along with what they do: msvbvm60: visual basic support, should be fine oleaut32, ole32, rpcrt4: DCOM/OLE, should be fine netapi: networking API (16 bit?), perhaps is not fine netapi32: ditto netbios.dll: almost certainly will not work msvcrt20: C library, should be fine So I'd update to the latest Wine, remove the net* dlls and try again. Let us know how you get on! thanks -mike
Am Fr, Dez 31, 2004 at 02:13:17 -0800 schrieb Mitchel Constantin:> client configuration with ltsp. So far I am using SUSE 9.1 to test and > everything runs great as far as this is concerned.This is a good approach. 9.2 is reasonable better, though. An easy thin client setup can be performed with Knoppix. You can have it on a server with the Knoppix network boot system and all your clients will be knoppix clients. A recent wine is installed there, too.> The problem runs in that the school requires a certain piece of > software that they use to manage their business processes (attendance, > billing, etc). I've been playing with WINE and have come very close to > getting the system to work. The software has been running on a Windows > 95 computer quite well and so I copied over the application directory > and then through a lot of trial and error I settled on what I believe > to be the right DLLs that were necessary from the Windows\System32 > directory from one of our Windows 95 computers.1. use win-20041019 2. use WineTools (http://www.von-thadden.de/Joachim/WineTools/) to get a usable setup and config 3. go through the whole Base setup, creating a new .wine and installing DCOM98 and IE6 as a basis for further installations 4. without changing anything try to *install* your program from the original media 5. send bug report to the list Regards Joachim -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"
Now then, heres an update on my situation, hopefully this thread isn't
old enough to slip through the cracks yet. I know it is long, but
please take a minute or two to read through it.
I spent majority of my time since my last message to the list
wrestling with Novell's site (very poor connection quality) to
download SUSE Linux Enterprise Server so that I could set up a proper
test machine with a newer kernel and packages. I then installed it
SLES, LTSP and WINE from their respective sites. The WINE version I
grabbed was 20041201. I followed Joachim's suggestion to install from
the CD and it worked (the install for ProCare).
The situation I face is that we are currently using software called
ProCare and are planning a switch to another called DCMS. ProCare so
far seems to be running properly, I can't actually log in to it yet
until tomorrow as I have to activate it via their telephone support
and due to the holidays they are closed. We will need to run both side
by side for a time. The more urgent matter is getting DCMS to work.
Installing DCMS from the CD leaves me with two seperate problems. For
clarity the messages in quotes are from message boxes that the program
itself pops up. Following them if relevant is the console output from
wine.
Error #1 occurs the first time WINE is run on Setup.exe and says:
"Error extracting Support files. (0x8003004)"
tree:/media/cdrom # wine Setup.exe
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
[this message is repeated about 50 times]
fixme:ole:ITypeInfo_fnRelease destroy child objects
err:ole:MARSHAL_Register_Proxy Already have mid?
fixme:ole:CoUnmarshalInterface Failed to create instance of
unmarshaller {0000030b-0000-0000-c000-000000000046}.
fixme:ole:_unmarshal_interface Marshalling interface
{aa7e2068-cb55-11d2-8094-00104b1f9838} failed with 800401f0
fixme:ole:deserialize_param failed to stuballoc in TKIND_RECORD.
fixme:ole:TMStubImpl_Invoke Failed to deserialize param
pTransferEvents, hres 800401f0
fixme:ole:CoUnmarshalInterface Failed to create instance of
unmarshaller {0000030b-0000-0000-c000-000000000046}.
fixme:ole:_unmarshal_interface Marshalling interface
{aa7e2068-cb55-11d2-8094-00104b1f9838} failed with 800401f0
fixme:ole:deserialize_param failed to stuballoc in TKIND_RECORD.
fixme:ole:TMStubImpl_Invoke Failed to deserialize param
pTransferEvents, hres 800401f0
fixme:ole:PipeBuf_Release Free all stuff
[this message is repeated about 10 times]
fixme:ole:PipeBuf_Release Free all stuff
tree:/media/cdrom # fixme:ole:read_pipe Read only 0 of 4 bytes from 0x54.
fixme:ole:_StubReaderThread Failed with hres 80004005
Error #2 happens when I run the Setup.exe again off of the CD and
after the first error:
"Error Installing iKernel.exe(0x1400)"
This second error can be fixed with a simple killall wine-server
before I start the DCMS Setup.exe again.
For DCMS copying the installation folder from a windows system's hard
drive to the server and attempting to run an exe from the bin folder
directory gives me some encouragement. The program appears to start
properly until I receive an error saying "Can not load the program,
contact OT, Inc." including this debug from wine:
tree:~/.wine/drive_c/DCMS9003/Bin # wine DCMS9003.exe
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:MSFT_ReadValue BSTR length = -1?
fixme:ole:MSFT_ReadValue BSTR length = -1?
fixme:ole:ITypeLibComp_fnBind (L"Date", 103b0a, 0x3, 0x4068dff4,
0x4068e010, 0x4068dff8): stub
fixme:ole:ITypeLibComp_fnBind (L"Date", 103b0a, 0x3, 0x4068ef04,
0x4068ef20, 0x4068ef08): stub
fixme:ole:OLEPictureImpl_Construct Unsupported type 3
fixme:ole:OleLoadPictureEx
(0x412b29fc,105697,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x4068f7cc),
partially implemented.
fixme:ole:OLEPictureImpl_get_hPal (0x403b5dd0)->(0x4068f778): stub
fixme:ole:OleLoadPictureEx
(0x412b5fa4,774,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x4068f82c),
partially implemented.
fixme:ole:OLEPictureImpl_FindConnectionPoint tried to find connection
point on {33ad4f92-6699-11cf-b70c-00aa0060d393}?
fixme:ole:OLEPictureImpl_FindConnectionPoint tried to find connection
point on {33ad4ed2-6699-11cf-b70c-00aa0060d393}?
fixme:ole:CoDisconnectObject (0x40367008, 0): stub - probably harmless
fixme:ole:CoDisconnectObject (0x403e8e58, 0): stub - probably harmless
fixme:ole:ITypeInfo_fnRelease destroy child objects
[this message is repeated about 20 times]
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:CoRegisterMessageFilter stub
tree:~/.wine/drive_c/DCMS9003/Bin #
Last thing that I noticed is the ProCare software (what few parts I
can access without the license) runs somewhat sluggishly. The computer
has a 2.8 P4 & 512MB of RAM. I understood from the WINE FAQ that the
applications should run at a comparable speed to running natively on
windows.
Thank you in advance for your comments, suggestions, and help,
Mitchel
> On Mon, 03 Jan 2005 19:48:56 -0800, Scott Ritchie wrote: > > To do it, try grabbing the winetools program and use it to install > > DCOM95. Then try installing the stuff again.WineTools installs DCOM98, not 95. And it brings a reasonable config. Regards Joachim -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"