Hi -
I am trying to run some software that expects the "OSNAME" to be "WINDOWS." (I am not saying there is a variable of "OSNAME", but that's what the error message I get uses.)
Now it turns out that by changing the Windows Version in winecfg I can change this value (e.g., "Windows7" gives "NET_SRV", "Windows 98" gives "WIN_98"). But none of the available options appear to correspond to plain "WINDOWS."
I checked in regedit but couldn't find anything. Also grep'ed Wine source code for the OSNAME values appear to be supported, but couldn't find them either.
Any help or pointers where I might look further are greatly appreciated!
Torsten
Configure "OSNAME" to be "WINDOWS"
-
- Newbie
- Posts: 3
- Joined: Tue Sep 17, 2013 12:55 pm
Re: Configure "OSNAME" to be "WINDOWS"
What Wine version? Post terminal output. http://wiki.winehq.org/FAQ#get_log
-
- Newbie
- Posts: 3
- Joined: Tue Sep 17, 2013 12:55 pm
Re: Configure "OSNAME" to be "WINDOWS"
Wine version is current as distributed with Fedora 19: wine-1.7.1-2.fc19.x86_64
Is as follows:
Thanks!
Torsten
Is as follows:
Code: Select all
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
fixme:ole:CLSIDFromProgIDEx L"Scripting.FileSystemObject",0x33faf4: semi-stub
fixme:scrrun:filesys_QueryInterface Unsupported interface {7fd52380-4e07-101b-ae2d-08002b2ec713}
fixme:scrrun:filesys_QueryInterface Unsupported interface {37d84f60-42cb-11ce-8135-00aa004bb851}
fixme:ole:CLSIDFromProgIDEx L"WScript.Shell",0x33faf4: semi-stub
fixme:wshom:WshShell3_QueryInterface Unknown iface {7fd52380-4e07-101b-ae2d-08002b2ec713}
fixme:wshom:WshShell3_QueryInterface Unknown iface {37d84f60-42cb-11ce-8135-00aa004bb851}
fixme:olepicture:OleLoadPictureEx (0xa5e394,2742,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x33f974), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xa5e394,17042,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x33f944), partially implemented.
fixme:olepicture:OLEPictureImpl_SaveAsFile (0x172198)->(0x187510, 0, (nil)), hacked stub.
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
fixme:olepicture:OleLoadPictureEx (0xa63dbc,3246,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x33e808), partially implemented.
fixme:olepicture:OLEPictureImpl_SaveAsFile (0x1ae8a0)->(0x19a360, 0, (nil)), hacked stub.
fixme:wshom:WshShell3_RegRead (L"HKEY_LOCAL_MACHINE\\SOFTWARE\\SAS Institute Inc.\\The SAS System\\9.1\\DefaultRoot" 0x33e708): stub
fixme:wshom:WshShell3_RegRead (L"HKEY_LOCAL_MACHINE\\SOFTWARE\\SAS Institute Inc.\\SAS 64 System\\9.1\\DefaultRoot" 0x33e708): stub
fixme:olepicture:OleLoadPictureEx (0xa64344,3246,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x33eba0), partially implemented.
fixme:olepicture:OLEPictureImpl_SaveAsFile (0x1f8c60)->(0x1ffd50, 0, (nil)), hacked stub.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
fixme:advapi:RegisterEventSourceA ((null),"SAS"): stub
fixme:advapi:RegisterEventSourceW (L"",L"SAS"): stub
fixme:advapi:RegisterEventSourceA ((null),"SAS"): stub
fixme:advapi:RegisterEventSourceW (L"",L"SAS"): stub
fixme:event:wait_for_withdrawn_state window 0x20110/6000002 wait timed out
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
Torsten
-
- Newbie
- Posts: 3
- Joined: Tue Sep 17, 2013 12:55 pm
Re: Configure "OSNAME" to be "WINDOWS"
Okay, this was a stupid question - sorry for wasting everyone's time.
The OSNAME constants were coded into the program that I was trying to run. They're not actually provided by Wine at all, but are determined by the application program based on some opaque tests and lookup tables.
Again, sorry for asking a stupid question.
TR
The OSNAME constants were coded into the program that I was trying to run. They're not actually provided by Wine at all, but are determined by the application program based on some opaque tests and lookup tables.
Again, sorry for asking a stupid question.
TR