Bard Posted June 27, 2008 Share Posted June 27, 2008 Brand new PC - fresh OS install.Installed the latest version of the codemeter control software - it is seeing the stick etc.Launching the steel beasts shortcut results in the error message in the title.I'll do some more digging about the forums but if anyone has a pointer i'd appreciate it. 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted June 27, 2008 Members Share Posted June 27, 2008 Hm. This is a bit troubling. There are a number of people lately reporting problems. So I wonder how many people actually do run SB Pro in a 64 bit environment - and which version of the CodeMeter runtime they have installed. Maybe 3.20 installed just nicely, but 3.30 won't work? 0 Quote Link to comment Share on other sites More sharing options...
Pteradon Posted June 27, 2008 Share Posted June 27, 2008 I run SBpro in Vista Ultimate x64, with SP1 installed.The Codemeter version i'm using is 3.30.The only problem i did encounter,http://www.steelbeasts.com/sbforums/showthread.php?t=11805 0 Quote Link to comment Share on other sites More sharing options...
Bard Posted June 27, 2008 Author Share Posted June 27, 2008 I've disabled UAC and tried launching as admin etc. Do we have a date that people started reporting the problems with vista 64? Perhaps there was a windows update that started mucking things up. I would ASSUME (with all associated problems ) that whatever query the sim launcher is making to the WIBU runtime is being blocked in some manner. Is there a way to log the requests being made from SB to the WIBU app? From other posts I would assume that the communcation is happening on a networking level - my box has dual NIC's (one is disabled) - could it be that the exe is trying to communicate through that device and failing? 0 Quote Link to comment Share on other sites More sharing options...
Administrators Sean Posted June 27, 2008 Administrators Share Posted June 27, 2008 Yes - it works over the network to make the request, I believe. The problems all seem to have started when the latest codemeter runtime came out. 0 Quote Link to comment Share on other sites More sharing options...
Bard Posted June 27, 2008 Author Share Posted June 27, 2008 ok uninstalled the extra NIC (uninstall in device manager) - no go. 0 Quote Link to comment Share on other sites More sharing options...
Bard Posted June 27, 2008 Author Share Posted June 27, 2008 ipconfig info:**************Windows IP Configuration Host Name . . . . . . . . . . . . : Uber Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-18-F3-00-BC-79 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b90b:47d8:a9d1:daf3%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.100.102(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 192.168.100.10 192.168.100.1 NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes******************Is it the teredo tunneling pseudo interface?Wondering if it is and being the '11th' network adapter is pushing it out of range. 0 Quote Link to comment Share on other sites More sharing options...
Fabfire Posted June 28, 2008 Share Posted June 28, 2008 Hm. This is a bit troubling. There are a number of people lately reporting problems. So I wonder how many people actually do run SB Pro in a 64 bit environment - and which version of the CodeMeter runtime they have installed. Maybe 3.20 installed just nicely, but 3.30 won't work?Ssnake, I am running SB ProPE in Windows XP x64. Using CodeMeter Runtime 64 v3.30a. No problems whatsoever. 0 Quote Link to comment Share on other sites More sharing options...
Bard Posted September 9, 2008 Author Share Posted September 9, 2008 My problem was caused by the WIBU runtime NOT being compatible with versions earlier than the latest beta.Once I installed the beta patch things worked. 0 Quote Link to comment Share on other sites More sharing options...
Dachs Posted October 6, 2008 Share Posted October 6, 2008 My problem was caused by the WIBU runtime NOT being compatible with versions earlier than the latest beta.Once I installed the beta patch things worked.Just posting to confirm the above.. NoGo with 2.328 but the Beta runs just fine! 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.