Jump to content

Bard

Members
  • Content Count

    29
  • Joined

  • Last visited

About Bard

  • Rank
    Junior Member

Personal Information

  • Location
    vancouver
  • Occupation
    IT guy
  1. yeah Il2 is definitely my most active sim - 3 nights a week in forgotten skies.
  2. I've just ordered the update and am looking to get back into SB. Any other west coasters here interested in doing a regular monday night thing?
  3. 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.
  4. Either Spits vs 109's or Zeke's vs Wildcats.
  5. Bard

    Hitler Kaput!

    It's kind of tragic how many people obtain all their historical information through BS - not knowing that for the past 50 years or so there's been a steady stream of it peddaled by the privately owned mainstream media for two particular agendas. It's even more tragic when people attack others who show some awarenes of what the hell is going on in the world with rudeness and derogatory comments because they've been conditioned to attack anyone with an opposing point of view (fox news anyone?) rather than examine and consider it and see if it is SENSIBLE
  6. it gives them their differential and me some fun!
  7. ok just tried with the beta and it works! (installed beta to default path, launched it) so - it's either pathing or it looks like the 3.30 software does not work with sb version 328.
  8. i went straight to the 64 bit version of codemeter (never had 32 bit installed). fresh install of vista 64 update all drivers for hardware and OS components install codemeter runtime (latest version, 3.30a) reboot insert usb key identified successfully install steel beasts installed patches (but not the beta) have rebooted since and no success codemeter should confirm on a CLEAN OS install with 3.30a (rather than on top of a failed earlier version install) just in case 3.20c is still managing to put something 3.30a is dependent upon but not included in 3.30.
  9. If they have a debug util or anything else they need to run let me know.
  10. ipconfig info: ************** Windows IP Configuration Host Name . . . . . . . . . . . . : Uber Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet 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. . . . . . . . : Enabled Tunnel 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 . . . . : Yes Tunnel 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.
  11. ok uninstalled the extra NIC (uninstall in device manager) - no go.
  12. 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?
  13. ok - looks like same issue here - vista 64 etc if you need a differential to help diagnose. no firewall or antivirus (gaming box).
×
×
  • Create New...