Premise Premise under Wine in openSUSE

Motorola Premise
G

GraysonPeddie

Active Member
Hi. I'm running 64-bit version of openSUSE 11 under VirtualBox and before I begin, I'd like to point you to www.winehq.com in case you want to know.

Now, here is my result of installing Premise under Wine:

Code: 
GraysonPeddie@linux-uuh9:~/Desktop> cd Premise
GraysonPeddie@linux-uuh9:~/Desktop/Premise> wine setup.exe
wine: created the configuration directory '/home/GraysonPeddie/.wine'
ALSA lib pcm.c:2104:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so
ALSA lib pcm.c:2104:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so
Could not load Mozilla. HTML rendering will be disabled.
wine: configuration in '/home/GraysonPeddie/.wine' has been updated.
fixme:advapi:LookupAccountNameW (null) L"GraysonPeddie" (nil) 0x33f88c (nil) 0x33f890 0x33f884 - stub
fixme:advapi:LookupAccountNameW (null) L"GraysonPeddie" 0x12d0b8 0x33f88c 0x12c1a0 0x33f890 0x33f884 - stub
fixme:msi:msi_unimplemented_action_stub MigrateFeatureStates -> 1 ignored L"Upgrade" table values
err:richedit:ReadStyleSheet ReadStyleSheet: skipping optional destination
err:richedit:ReadStyleSheet ReadStyleSheet: skipping optional destination
fixme:msi:ACTION_HandleStandardAction unhandled standard action L"SetODBCFolders"
fixme:msi:msi_unimplemented_action_stub MigrateFeatureStates -> 1 ignored L"Upgrade" table values
fixme:msi:msi_unimplemented_action_stub RemoveExistingProducts -> 1 ignored L"Upgrade" table values
fixme:msi:msi_unimplemented_action_stub DeleteServices -> 3 ignored L"ServiceControl" table values
fixme:msi:msi_unimplemented_action_stub RemoveShortcuts -> 7 ignored L"Shortcut" table values
fixme:shell:DllCanUnloadNow stub
fixme:msi:ITERATE_InstallService Dependency list unhandled!
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program Files\\Premise\\SYS\\bin\\sysrap.tlb" failed with error 2
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0042, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0044, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0043, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0040, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 003f, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0041, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 003b, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 003e, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0038, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0037, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 0039, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 003c, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 003d, blocked by 0036, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc95564 "loader.c: loader_section" wait timed out in thread 003a, blocked by 0036, retrying (60 sec)
fixme:win:RegisterDeviceNotificationA (hwnd=0x1292e0, filter=0x7e09d9ac,flags=0x00000001),
	returns a fake device notification handle!
fixme:ole:CoInitializeSecurity (0x129800,-1,(nil),(nil),4,3,(nil),0,(nil)) - stub!
fixme:advapi:RegisterEventSourceA ((null),"PRKERNEL"): stub
fixme:advapi:RegisterEventSourceW (L"",L"PRKERNEL"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0021,0x00000129,(nil),0x0001,0x00000000,0x7e09d930,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0021,0x00000129,(nil),0x0001,0x00000000,0x12e980,(nil)): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
fixme:msxml:domdoc_QueryInterface interface {7fd52380-4e07-101b-ae2d-08002b2ec713} not implemented
fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set
fixme:shell:DllCanUnloadNow stub
fixme:advapi:RegisterEventSourceA ((null),"PRKERNEL"): stub
fixme:advapi:RegisterEventSourceW (L"",L"PRKERNEL"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0002,0x0021,0x00000147,(nil),0x0004,0x00000050,0x7e09cc64,0x7e09d190): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0002,0x0021,0x00000147,(nil),0x0004,0x00000050,0x179898,0x7e09d190): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set
GraysonPeddie@linux-uuh9:~/Desktop/Premise>

I'm going to try to run Premise to see what the result will be.
 
I tried to run Premise Builder under Wine in openSUSE and it won't let me go any further. It hangs up in splash screen.

Update: Okay, here's my result of running Premise Builder (I renamed the shortcut to premisebuilder; note that it's case-sensitive uner Linux):

Code: 
GraysonPeddie@linux-uuh9:~/Desktop> wine premisebuilder
fixme:win:RegisterDeviceNotificationA (hwnd=0x129ab8, filter=0x7e0ab9ac,flags=0x00000001),
		returns a fake device notification handle!
fixme:ole:CoInitializeSecurity (0x129fe8,-1,(nil),(nil),4,3,(nil),0,(nil)) - stub!
fixme:advapi:RegisterEventSourceA ((null),"PRKERNEL"): stub
fixme:advapi:RegisterEventSourceW (L"",L"PRKERNEL"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0021,0x00000129,(nil),0x0001,0x00000000,0x7e0ab930,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0021,0x00000129,(nil),0x0001,0x00000000,0x12f1c0,(nil)): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
fixme:msxml:domdoc_QueryInterface interface {7fd52380-4e07-101b-ae2d-08002b2ec713} not implemented
fixme:ole:CoInitializeSecurity (0x122598,-1,(nil),(nil),4,3,(nil),0,(nil)) - stub!
fixme:advapi:RegisterEventSourceA ((null),"PSMONITOR"): stub
fixme:advapi:RegisterEventSourceW (L"",L"PSMONITOR"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0020,0x00000102,(nil),0x0000,0x00000000,(nil),(nil)): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
wine: could not load L"C:\\windows\\system32\\premisebuilder.exe": Module not found
GraysonPeddie@linux-uuh9:~/Desktop> fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set
fixme:advapi:RegisterEventSourceA ((null),"PRKERNEL"): stub
fixme:advapi:RegisterEventSourceW (L"",L"PRKERNEL"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0002,0x0021,0x00000147,(nil),0x0004,0x00000050,0x7e0aac64,0x7e0ab190): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0002,0x0021,0x00000147,(nil),0x0004,0x00000050,0x17a2c0,0x7e0ab190): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub

It stucked there forever.
 
Well that didn't go very smoothly! It's too bad this wasn't successful because Wine would give Premise a place to run without Win XP. I guess when a Windows app fails to run in an emulated Windows environment, there's not much to do except try to tweak the environment.

Other than its intended purpose, I don't know much about Wine; however, there are a few error messages in the list that caught my eye.

In the first list, there are references to components (snd_pcm_open_conf and Mozilla) that could not be opened. Is it possible some parts of Wine are missing?
In the second list, there's an odd reference to premisebuilder.exe in the system32 folder. Normally Builder is in the \Program Files\Premise\SYS folder. Something appears to have messed up during the installation process.
 
Do you have a Linux box you can try out? Or do you have enough RAM to try out Ubuntu or openSUSE in a vurtual machine?

Hmm... seems to me I need to install Firefox under Wine, but why would I want to do that?
snd_pcm_open_conf? I have no idea what that is...

I don't have the complete knowledge of Linux, but I got around openSUSE just fine.

I would have hope that mSense is free of a patent and that Premise gets open-sourced. But that will never happen.
 
Don't know anything about Wine yet, but how does it deal with hardware? Can it pass the hardware access through to Windows apps? Like the sound cards, etc.?

Have you thought about running a Virtual Machine with actual Windows XP running within?

I am running the other way right now, using my Windows XP box running Premise and SageTV natively with a VM running CentOS linux and a Zimbra mail server. Works great. So I would think that the other way would work as well.

Unless of course the idea is to stay clear of Microsoft ;) Or if you're feeling really gutsy, try ReactOS. It's in Alpha, but aims to be a fully compatible Windows XP clone. Haven't had a chance to try it yet, but I've been following it.
 
I think ReactOS is far from being alpha. I wish it includes Mozilla Firefox 3.0... The development of ReactOS is too slow and too much of a regression (due to six-month period) for me to consider go with the operating system.

Due to my financial woes, I can't afford Windows right now, even with my financial aid, because I've got moving expenses coming up (U-Hal) and I'm saving up my money.
 
OK. Ignore my comment about Firefox 3.

I started ReactOS, clicked in "Download !" to download Firefox 2.0 and 7-Zip, I downloaded Premise and the install seems to went fine, but I'm not very sure about that because I think there may be installation problems.

Once I run Premise Builder, I am prompted to download the Mozilla ActiveX component (!!!). Once it's finished, I get this:

The instruction at "0x608ae05e" referenced memory at "0x00000000". The memory could not be "read".

Click Cancel or OK, run again, and the message is the same as above.
 
It sounds like you're making progress but some parts are still missing.

You indicated Builder prompted to download the Mozilla ActiveX component. Builder looks a lot like Visual Studio's IDE (the older version) and has a browser window. On startup, it used to display the Premise web-site but that site is gone so nowadays you just get an error page. I don't think Premise Builder has a native browser-engine but simply uses the operating system's default browser-engine ... in this case, under ReactOS, I guess it defaults to Mozilla. It appears it is having trouble locating Mozilla.

BTW, if you get Mozilla straightened out, the first time you point your browser to the Premise server (port 80 by default or 86 if 80 is already in use), it will inform you it needs to download an ActiveX component. Premise uses this component to update the status of each displayed object (otherwise, it would have to resort to periodic page-refreshes). All of this stuff was designed to work with Internet Explorer. I've never tried it with Firefox, but I learned in another post that FireFox has an IE compatibility mode ... maybe that could work.

Good luck with your experimentation; I doubt anyone has tried this before so you're definitely in unexplored territory!

PS, Premise will run on old hardware equipped with Windows 2000. If your budget is tight, consider using an old PC; somewhere, somone you know may have one collecting dust that can be reclaimed for use with Premise. FWIW, my Premise server is an 866MHz Pentium 3 with 256Mb RAM and Win XP.
 
Ok. I downloaded Firefox 3.0 into ReactOS, installs with no problems, and when running Firefox 3.0, it's got rendering problems with the toolbar and overlapped text.

Now, Premise Builder gave me a different effect. It prompted me (even before and after the install of Firefox 3.0) to download the ActiveX plug-in for Mozilla, and it gave me this:

www.{00000000-0001-0025-1999-23865e9a5812}.com could not be found. Please check the name and try again.

So, I clicked OK, waited one minute, and this tells me there's no hard drive activity going on. So, I restart ReactOS. Yep. You guessed it: that same message came back again, so when I click OK, I waited, but it will stay there forever until I end the process.

Not everyone in my family or my relatives have an old hardware, but I'll ask my mom. Even if I do, there's an 80% chance that my family does not have any old hardware.
 
Grayson Peddie said:
www.{00000000-0001-0025-1999-23865e9a5812}.com could not be found
Click to expand...
I think that should say "www.premisesystems.com". Yeah, there's no polite way to put it other than it's all FUBAR. ;)

Every object in Premise has a unique identifier called a GUID. When you tell Builder to make a backup, it dumps everything out to a file in XML format. Browsing through this file reveals each object's GUID. The last data-set in the GUID you described (i.e. "23865e9a5812") occurs frequently and appears to be associated with a property's type ... like is the value integer, string, boolean, etc. "Fascinating" ... but it provides no clue as to why this errant GUID is popping up in the middle of a URL!

PS
If you're willing to make a phone calls, consider contacting the large corporations in your area; ask to speak to the IT Manager. Unless they lease their PCs, there's a good chance they have some old codgers lying around in a storage room (fully depreciated but no one found time to get rid of them). Tell them you offer free pickup of castoffs and you may hit pay dirt. Back when I was an IT Director, my department held an annual PC sale. We cleared out our inventory of outdated gear (three years and older), got a lot of positive feedback from employees, and all proceeds were donated to charity.
 
I know about the GUID when it comes to C#. Thanks.

Update: I'm a college student and I'm hearing impaired, but thanks for offering suggestions.

Well, I guess I'll have to waste my money and purchase Windows Home Server for $190... I really wanted features from Windows Server 2003, but I can't afford it...

Oh, and like I said, I'm going through financial difficulties. I wanted to stay cheap or as close to be free as possible for software.

There has got to be something very similar to Premise under Linux.
 
You must log in or register to reply here.
Back
Top