I had the latest wine running under winblows 98 SE for a week or two with no problems, then I installed winblows 2000 and now I cannot get wine to work. It is important for me to get it running again since I run United Devices cancer research agent (http://members.ud.com) 24/7 to help them find a cure for cancer. Is wine compatible with Win2k, or will I need to re-install 98 again? -- Interested in finding a cure for cancer? http://members.ud.com/services/teams/team.htm?id=2910655E-026A-47F8-A1CE-C45 B9BAAB072-
On Sat, 8 Sep 2001, Scott wrote:> I had the latest wine running under winblows 98 SE for a week or two with no > problems, then I installed winblows 2000 and now I cannot get wine to work. > It is important for me to get it running again since I run United Devices > cancer research agent (http://members.ud.com) 24/7 to help them find a cure > for cancer. Is wine compatible with Win2k, or will I need to re-install 98 > again? > --I see no one has taken the trouble to bite your head off, so I guess it is my turn. You did not ever run Wine under any flavor of winblows, unless maybe you used vmware for winblows to do it. Wine is a *nix (linux, FI) application program and library that provides the winblows API to winblows applications. For those applications, Wine _is_ winblows, of whichever --winver the Wine Administrator tells it to be. Neither does Wine run winblows. It has no use at all for the core winblows dlls - kernel32, gdi32, user32, except insofar as some application might want to check if they are there and read version information from them. If they are not there, Wine will make up version information. win2000 dll's are more thoroughly booby-trapped than earlier windows versions, so you might have better success with something like this in ~/.wine/config: [DllOverrides] "*" = "builtin, so, native" [AppDefaults\\juno.exe\\DllOverrides] "msvcrt" = "native" "riched32" = "native" [AppDefaults\\netscape.exe\\DllOverrides] "msvcrt" = "native" Set AppDefaults for your own apps, of course, probably mine won't do you any good, but I don't think "*" = "native, builtin, so" will work very well with winblows 2000 any time soon. The main thrust of Wine development seems to be to get the wine builtin dll's working, not to be compatible with native dll's of any version. If our dll's work with Wine, why should we care if Mr. Bill's don't? Lawson ---oof---
"Scott" <notoriousiroc@purdue.edu> wrote in message news:<1d7c.3b9a33f9.341a@wine2.winehq.com>...> I had the latest wine running under winblows 98 SE for a week or two with no > problems, then I installed winblows 2000 and now I cannot get wine to work. > It is important for me to get it running again since I run United Devices > cancer research agent (http://members.ud.com) 24/7 to help them find a cure > for cancer. Is wine compatible with Win2k, or will I need to re-install 98 > again?I would to see how you managed to compile a un*x program to run under windows to *ultimately* *pointlessly* run windows programs through it? Although maybe those windoze executables are probably overjoyed for being run under a much more stable *patched* environment, I can't see how your CPU+RAM would even slightly be pleased at such a waste of time and space, so rid yourself of windoze and add a splash of colour to your system with Linux.
I would suggest you go back to 98 for now. Windoze 2000 is still rather new and it will require some time for wine to catch up to the many subtle and pointless changes made to the dlls and such that M$ made to them. I was having few problems with wine and 98 SE myself but then I upgraded my windoze to ME and poof! No more worky. Scott wrote:> I had the latest wine running under winblows 98 SE for a week or two with > no problems, then I installed winblows 2000 and now I cannot get wine to > work. It is important for me to get it running again since I run United > Devices cancer research agent (http://members.ud.com) 24/7 to help them > find a cure > for cancer. Is wine compatible with Win2k, or will I need to re-install > 98 again? > -- > Interested in finding a cure for cancer? >http://members.ud.com/services/teams/team.htm?id=2910655E-026A-47F8-A1CE-C45> B9BAAB072-
Would you be willing to email me (or post) a copy of your config file? I too use WIN98, but only a few programs actually work. IE5.5 opens, but does little else. OE5.5 will not open at all. Office 2000 programs all open, but cannot open or save files. I am sure my problems have something to do with my config file, but I cannot figure it out. I am using the latest version of Codeweaver on SuSe 7.1 and a WIN98SE partition on the same drive. Thanks -- Chuck Vinson Dayton OH Registered Linux User #214882 "Praedor Tempus" <praedor@uswest.net> wrote in message news:q%fo7.6170$Hp3.553357@news.uswest.net...> I would suggest you go back to 98 for now. Windoze 2000 is still rather > new and it will require some time for wine to catch up to the many subtle > and pointless changes made to the dlls and such that M$ made to them. > > I was having few problems with wine and 98 SE myself but then I upgradedmy> windoze to ME and poof! No more worky. > > Scott wrote: > > > I had the latest wine running under winblows 98 SE for a week or twowith> > no problems, then I installed winblows 2000 and now I cannot get wine to > > work. It is important for me to get it running again since I run United > > Devices cancer research agent (http://members.ud.com) 24/7 to help them > > find a cure > > for cancer. Is wine compatible with Win2k, or will I need to re-install > > 98 again? > > -- > > Interested in finding a cure for cancer? > > >http://members.ud.com/services/teams/team.htm?id=2910655E-026A-47F8-A1CE-C45> > B9BAAB072- >
If the apps that you want to run are things like Office you are better off using Win4Lin or vmware. I use wine for applications that require large amounts of memory (Win4Lin is limited to 64M) and consist of single executables, i.e. they are not large collections of DLLs. For me that means Xilinx place and route tools which started life as Unix apps and are ported to Windoze. For true Windows apps like Word or Acrobat Distiller I use WIn4Lin I find that Win4Lin is the best solution. In <3ba1ca50$0$1526$4c5ecdc7@news.erinet.com>, Charles Vinson wrote:> Would you be willing to email me (or post) a copy of your config file? I > too use WIN98, but only a few programs actually work. IE5.5 opens, but > does little else. OE5.5 will not open at all. Office 2000 programs all > open, but cannot open or save files. I am sure my problems have > something to do with my config file, but I cannot figure it out. I am > using the latest version of Codeweaver on SuSe 7.1 and a WIN98SE > partition on the same drive. Thanks > -- > Chuck Vinson > Dayton OH > Registered Linux User #214882 > > "Praedor Tempus" <praedor@uswest.net> wrote in message > news:q%fo7.6170$Hp3.553357@news.uswest.net... >> I would suggest you go back to 98 for now. Windoze 2000 is still >> rather new and it will require some time for wine to catch up to the >> many subtle and pointless changes made to the dlls and such that M$ >> made to them. >> >> I was having few problems with wine and 98 SE myself but then I >> upgraded > my >> windoze to ME and poof! No more worky. >> >> Scott wrote: >> >> > I had the latest wine running under winblows 98 SE for a week or two > with >> > no problems, then I installed winblows 2000 and now I cannot get wine >> > to work. It is important for me to get it running again since I run >> > United Devices cancer research agent (http://members.ud.com) 24/7 to >> > help them find a cure >> > for cancer. Is wine compatible with Win2k, or will I need to >> > re-install 98 again? >> > -- >> > Interested in finding a cure for cancer? >> > >> > > http://members.ud.com/services/teams/team.htm?id=2910655E-026A-47F8-A1CE-C45 >> > B9BAAB072- >>