Newest WINE No Longer Runs

JWilliamCupp · Post by **JWilliamCupp** » Thu Mar 27, 2008 9:09 pm

I have a Dell Laptop running Fedora 7. I bought this from "Emperor Linux" who configured the machine and shipped it to me ready-to-go.

I had successfully installed a few minor Windows applications and had them running under WINE. Since I began using Linux a few years ago, I have adopted the posture of doing periodic updates with yum.

Awhile ago, one such yum update installed WINE 0.9.54 and everything stopped working then. By now I am up to WINE 0.9.56, but no WINE application runs.

Can someone help me troubleshoot this and see if I can figure out what went wrong?

When I try to open anything in WINE from a console, I get a long string of error messages, but I don't know where to go with this. Here is an example -- I think the errors are the same for any application, but I can't say for sure.

Example error dump:
-----------------------------------
$ wine bksetup6.EXE
fixme:spoolsv:serv_main (0 (nil))
err:advapi:service_get_status service protocol error - failed to read pipe r = 0 count = 0!
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:win:User32InitializeImmEntryTable (0x19650412): stub
fixme:ntdll:NtConnectPort (0x5ada1170,L"\\ThemeApiPort",0x33f258,(nil),(nil),(nil),0x33f268,0x33f264),stub!
fixme:crypt:I_CryptCreateLruCache (0x33e850, 0x76c5a018): stub!
fixme:crypt:I_CryptInstallAsn1Module (0x176cc0 00000000 (nil)): stub
fixme:advapi:RegisterEventSourceW ((null),L"Print"): stub
fixme:winsock:convert_af_w2u unhandled Windows address family 26
fixme:winsock:WSASocketW Unsupported socket family -1!
fixme:winsock:convert_af_w2u unhandled Windows address family 26
fixme:winsock:WSASocketW Unsupported socket family -1!
fixme:winsock:convert_af_w2u unhandled Windows address family 26
fixme:winsock:WSASocketW Unsupported socket family -1!
fixme:ole:NdrCorrelationInitialize (0x33e4d8, 0x33e0d8, 1024, 0x0): stub
fixme:profile:CloseProfileUserMapping (), stub!
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
fixme:winspool:AddPrinterW Can't create printer L"CenterSchool_MATCIS_CP1"
err:winspool:CUPS_LoadPrinters printer 'CenterSchool_MATCIS_CP1' not added by AddPrinterA (error 1801)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
fixme:winspool:AddPrinterW Can't create printer L"CenterSchool_MATCIS_CP2"
err:winspool:CUPS_LoadPrinters printer 'CenterSchool_MATCIS_CP2' not added by AddPrinterA (error 1801)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
fixme:winspool:AddPrinterW Can't create printer L"Deskjet_F300_series"
err:winspool:CUPS_LoadPrinters printer 'Deskjet_F300_series' not added by AddPrinterA (error 1801)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
fixme:winspool:AddPrinterW Can't create printer L"Desktjet_F300_for_Windows"
err:winspool:CUPS_LoadPrinters printer 'Desktjet_F300_for_Windows' not added by AddPrinterA (error 1801)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
err:winspool:CUPS_LoadPrinters printer 'HP1209' not added by AddPrinterA (error 1797)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
err:winspool:CUPS_LoadPrinters printer 'HP1209-Windows' not added by AddPrinterA (error 1797)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
fixme:winspool:AddPrinterW Can't create printer L"psc_1200_series"
err:winspool:CUPS_LoadPrinters printer 'psc_1200_series' not added by AddPrinterA (error 1801)
fixme:advapi:ObjectOpenAuditAlarmW stub (L"Spooler",0x520158,L"Server",L"\\\\PoundFoolish",0x177688,0xfc,0x00000001,0x00000001,(nil),0,1,0x75bfb4fc)
fixme:advapi:ObjectCloseAuditAlarmW stub (L"Spooler",0x520158,0)
err:winspool:add_printer_driver Failed adding driver "wineps.drv" ("Windows NT x86"): 1805
err:winspool:CUPS_LoadPrinters printer 'psc_1200_series@Home_Linux' not added by AddPrinterA (error 1797)
err:winmm:MMDRV_InitPerType Strange: mapper with 8 > 1 devices
-----------------------------------

Help!

- Bill

Dan Kegel · Post by **Dan Kegel** » Thu Mar 27, 2008 10:47 pm

On Thu, Mar 27, 2008 at 7:09 PM, JWilliamCupp <[email protected]> wrote:

Awhile ago, one such yum update installed WINE 0.9.54 and everything stopped working

Try this: rename your .wine directory to .wine.old.

It's possible that your .wine directory is old enough that
it's not compatible with current wine.
- Dan

Gerry Visel · Post by **Gerry Visel** » Thu Mar 27, 2008 10:54 pm

On Thu, 2008-03-27 at 20:47 -0700, Dan Kegel wrote:

On Thu, Mar 27, 2008 at 7:09 PM, JWilliamCupp <[email protected]> wrote:
Awhile ago, one such yum update installed WINE 0.9.54 and everything stopped working
Try this: rename your .wine directory to .wine.old.

It's possible that your .wine directory is old enough that
it's not compatible with current wine.
- Dan

Time for new wineskins???

JWilliamCupp · Post by **JWilliamCupp** » Fri Mar 28, 2008 5:34 am

Gerry Visel wrote:On Thu, 2008-03-27 at 20:47 -0700, Dan Kegel wrote:
Try this: rename your .wine directory to .wine.old.

It's possible that your .wine directory is old enough that
it's not compatible with current wine.
- Dan

That worked! thanks ....

So now do I have to re-install everything I had previously installed under WINE? Gosh, I hope this doesn't happen too often.

- Bill

austin987 · Post by **austin987** » Fri Mar 28, 2008 8:02 am

On Fri, Mar 28, 2008 at 5:34 AM, JWilliamCupp <[email protected]> wrote:

Gerry Visel wrote:

On Thu, 2008-03-27 at 20:47 -0700, Dan Kegel wrote:
Try this: rename your .wine directory to .wine.old.

It's possible that your .wine directory is old enough that
it's not compatible with current wine.
- Dan

That worked! thanks ....

So now do I have to re-install everything I had previously installed under WINE? Gosh, I hope this doesn't happen too often.

- Bill

You can try:
$ mv .wine.old .wine
$ wineprefixcreate

And see if your apps run, but if not, then just delete ~/.wine and
reinstall your apps.

JWilliamCupp · Post by **JWilliamCupp** » Fri Mar 28, 2008 8:03 am

JWilliamCupp wrote:So now do I have to re-install everything I had previously installed under WINE?

No, I figured it out. Hah!

I just copied .wine.old/c_drive over to .wine/c_drive and everything is back.

Much easier than I was concerned it would be.

- Bill

Dan Kegel · Post by **Dan Kegel** » Fri Mar 28, 2008 10:27 am

On Fri, Mar 28, 2008 at 6:03 AM, JWilliamCupp <[email protected]> wrote:

So now do I have to re-install everything I had previously installed under WINE?
No, I figured it out. Hah!

I just copied .wine.old/c_drive over to .wine/c_drive and everything is back.

Much easier than I was concerned it would be.

That might not fix all your apps, since it didn't bring back
any registry entries... but I'm glad it got you back up.

No, this shouldn't happen too often, and it shouldn't happen
at all when upgrading from one stable version of Wine (say 1.0.0)
to the next (say, 1.2.0).
- Dan