Author Topic: Win Orbiter won't start  (Read 2615 times)

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Win Orbiter won't start
« on: April 07, 2005, 09:52:13 am »
Hi,

I've installed win Orbiter (I guess I did it over older installation) and I spot similar behaviour as in Mobile Orbiter. Screen is garbled and it crashes, reporting problem.
Any advice ?

I get this in logger :

Code: newbielink:javascript:void(0); [nonactive]
9:46:29.311 Device: 6646 starting.  Connecting to: 192.168.0.3
9:46:29.311 Ready to call connect
9:46:29.311 about to cleanup 3
9:46:29.311 OrbiterSDL_Win32: need to cleanup orbiter...
9:46:29.311 OrbiterSDL_Win32 constructor.
9:46:29.471 Orbiter 00F2E148 constructor
9:46:29.471 Initialized SDL
9:46:29.551 Set video mode to 800 x 600 Window.
9:46:29.551 Created back screen surface!
9:46:29.561 Connect OK
9:46:29.561 Orbiter SelfUpdate: starting
9:46:29.561 Last update didn't failed.
9:46:29.571 CRITICAL : The MD5 file is missing.
9:46:29.571 No update available on the server.
9:46:29.571 CRITICAL : Directory: C6646/ doesn't contain the orbiter's .info file.  Requesting files from the server.
9:46:31.394 Executing 1 commands in object: 1881.0.0.3305.837
9:46:31.394 Executing command 254 in object: 1881.0.0.3305.837
9:46:31.394 Parm 3 = 1881.0.0.3305.837
9:46:31.394 Parm 14 = follow_security
9:46:31.404 Parm 104 = 1
9:46:31.414 Executing 1 commands in object: 1931.0.0.1809.909
9:46:31.414 Executing command 254 in object: 1931.0.0.1809.909
9:46:31.414 Parm 3 = 1931.0.0.1809.909
9:46:31.424 Parm 14 = housemode
9:46:31.424 Parm 104 = 0
9:46:31.474 Executing 1 commands in object: 2211.0.0.3302.1263
9:46:31.474 Executing command 254 in object: 2211.0.0.3302.1263
9:46:31.474 Parm 3 = 2211.0.0.3302.1263
9:46:31.474 Parm 14 = follow_light
9:46:31.474 Parm 104 = 1
9:46:31.484 Executing 1 commands in object: 2212.0.0.3303.1292
9:46:31.494 Executing command 254 in object: 2212.0.0.3303.1292
9:46:31.494 Parm 3 = 2212.0.0.3303.1292
9:46:31.494 Parm 14 = follow_climate
9:46:31.494 Parm 104 = 1
9:46:31.494 Executing 1 commands in object: 2213.0.0.3304.1297
9:46:31.494 Executing command 254 in object: 2213.0.0.3304.1297
9:46:31.494 Parm 3 = 2213.0.0.3304.1297
9:46:31.494 Parm 14 = follow_telecom
9:46:31.504 Parm 104 = 1
9:46:31.504 Executing 1 commands in object: 2228.0.0.3296.1318
9:46:31.504 Executing command 254 in object: 2228.0.0.3296.1318
9:46:31.504 Parm 3 = 2228.0.0.3296.1318
9:46:31.514 Parm 14 = follow_media
9:46:31.514 Parm 104 = 1
9:46:31.604 Get Floorplan layout found 0 pages
9:46:31.604 CMD_Goto_Screen: 1255.0.0
9:46:31.614 Need to change screens logged to 1255.0.0
9:46:31.614 Checing room: 238 ea 2 against 0 0
9:46:31.614 using location in size: 3
9:46:31.614 Checing room: 237 ea 1 against 0 0
9:46:31.614 Checing room: 239 ea 0 against 0 0
9:46:31.614 Need to change screens executed to 1255.0.0
9:46:31.614 @@@ About to call maint for screen saver with timeout: 600000 ms
9:46:31.614 Awoke with 1 pending
9:46:31.614 Changing screen to 1255.0.0
9:46:31.614 calling redraw
9:46:31.624 Awoke with 2 pending
9:46:31.624 In Redraw Objects: rerender 1
9:46:31.624 $$$ RENDER SCREEN $$$ 1255.0.0
9:46:31.634 Render screen: 1255.0.0
9:46:31.634 Rendering: 1255.0.0 hidden: 0
9:46:31.674 Receive string: MESSAGE 68            
9:46:31.684 Received MESSAGE 68             00F2E148 device: 6646
9:46:31.734 Received Message type 1 ID 242 from 6611 to 6646 (device: 6646)
9:46:31.734 calling redraw
9:46:31.684 Starting processing events
9:46:31.855 Receive string: MESSAGE 83            
9:46:31.855 Received MESSAGE 83             00F2E148 device: 6646
9:46:31.865 Received Message type 1 ID 26 from 6615 to 6646 (device: 6646)
9:46:31.865 calling redraw
9:46:31.865 Receive string: MESSAGE 74            
9:46:31.875 Received MESSAGE 74             00F2E148 device: 6646
9:46:31.875 Received Message type 1 ID 192 from 6646 to 6646 (device: 6646)
9:46:31.875 calling redraw
9:46:31.875 Receive string: MESSAGE 86            
9:46:31.885 Received MESSAGE 86             00F2E148 device: 6646
9:46:31.885 Received Message type 1 ID 26 from 6611 to 6646 (device: 6646)
9:46:31.885 calling redraw
9:46:31.885 Receive string: MESSAGE 86            
9:46:31.895 Received MESSAGE 86             00F2E148 device: 6646
9:46:31.895 Received Message type 1 ID 26 from 6611 to 6646 (device: 6646)
9:46:31.895 calling redraw
9:46:31.895 Receive string: MESSAGE 88            
9:46:31.905 Received MESSAGE 88             00F2E148 device: 6646
9:46:31.905 Received Message type 1 ID 26 from 6611 to 6646 (device: 6646)
9:46:31.905 calling redraw
9:46:31.905 Receive string: MESSAGE 89            
9:46:31.915 Received MESSAGE 89             00F2E148 device: 6646
9:46:31.915 Received Message type 1 ID 26 from 6611 to 6646 (device: 6646)
9:46:31.915 calling redraw
9:46:31.915 Receive string: MESSAGE 88            
9:46:31.925 Received MESSAGE 88             00F2E148 device: 6646
9:46:31.925 Received Message type 1 ID 26 from 6611 to 6646 (device: 6646)
9:46:31.925 calling redraw

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Win Orbiter won't start
« Reply #1 on: April 07, 2005, 10:11:27 am »
Nevermind,

I donwloaded from local Orbiters page and now it works. First was downloaded from Pluto (link that someone mentioned in earlier posts).

Regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Win Orbiter won't start
« Reply #2 on: April 07, 2005, 12:27:08 pm »
Hi Rob,

Please give us the link with the broken win Orbiter so we can fix it. Thanks.

Regars,
Chris. M