RogueSqdn

Removing the DVD burner didn't do any good, and now I'm down to 1 activation. I would very much appreciate if someone from ED could get this fixed. If it's something that can't be fixed publically, like me needing some kind of key.. just PM me. Please at least respond.

I suppose I could try that, but why should I have to undo any of my hardware? Dmut, I saw somewhere that a Starforce announcement is due soon... would anything apply here? Is this even Starforce related?

I don't think it's a Starforce issue, at least with activation. I HAVE made it to the LockOn main menu before... I had to wait more than an hour to do it though. Still haven't flown yet. EDIT: I haven't installed any of the Nero software that came with the burner.

Found a link on HP's website with my mobo details: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00022505&dlc=en&lc=en&product=374776&lang=en&cc=us&printable=yes&

System specs are in my signature. I'm behind a router, but no software firewall is running now. I have a DVD-ROM drive and a Sony Dual layer DVD burner. As stated before.. I have no idea what mobo this is and don't know how to find out. Starforce activation seemed to go ok. I can hear the "music" of LockOn and see it in the taskbar, but the LockOn menu is not showing.

Clean XP install did not work. I haven't even installed Norton yet, so I know that's not interfering. I'm now down to 2 activations left. I sure hope someone solves this. error log 4/10/2005 15:54 V502031740 system log Input focus: true DirectInput8Create() DirectInput8->EnumDevices() Input device found: Mouse Instance: 9421---1--668800 ProductName: Mouse Product: 9421---1--668800 Type: A mouse or mouse-like device (such as a trackball). Subtype: Subtype could not be determined. Detected: 8 buttons, 3 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Mouse added to list Using mouse elements: 8 buttons, 3 axes Input device found: Keyboard Instance: 9421---1--668800 ProductName: Keyboard Product: 9421---1--668800 Type: Keyboard or keyboard-like device. Subtype: IBM PC Enhanced 101/102-key or Microsoft Natural® keyboard. Detected: 128 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Keyboard added to list Input device found: Logitech Cordless USB Mouse & Enhanced Keys Instance: ---5---1-1668800 ProductName: Logitech Cordless USB Mouse & Enhanced Keys Product: 141-000000876876 Type: Device that does not fall into another category. Detected: 255 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Input device found: Logitech Cordless USB Mouse & Enhanced Keys Instance: ---5---1-2668800 ProductName: Logitech Cordless USB Mouse & Enhanced Keys Product: 141-000000876876 Type: Device that does not fall into another category. Detected: 3 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Input device found: Logitech Cordless USB Mouse & Enhanced Keys Instance: ---5---1-3668800 ProductName: Logitech Cordless USB Mouse & Enhanced Keys Product: 141-000000876876 Type: Device that does not fall into another category. Detected: 0 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Input device found: Xkeys Matrix Instance: 354----1-6668800 ProductName: Xkeys Matrix Product: -592000000876876 Type: Device that does not fall into another category. Detected: 128 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Input device found: Xkeys Instance: 354----1-7668800 ProductName: Xkeys Product: -5-2000000876876 Type: Device that does not fall into another category. Detected: 88 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Input device found: CH Control Manager Device 1 Instance: -814---1-1668800 ProductName: CH Control Manager Device 1 Product: -61-000000876876 Type: Joystick. Subtype: Joystick that does not provide the minimum number of device objects for action mapping. Detected: 0 buttons, 5 axes, 1 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Joystick added to list Found joystick element: X Axis Smoother created: X Smoother x 0 Found joystick element: Y Axis Smoother created: Y Smoother y 4 Found joystick element: Z Axis Smoother created: Z Smoother z 8 Found joystick element: Z Rotation Smoother created: rZ Smoother rz 20 Found joystick element: Slider Smoother created: S Smoother slider 24 Found joystick element: Hat Switch Found joystick element: Collection 0 - Joystick GUID_Unknown detected Using joystick elements: 0 buttons, 5 axes, 1 povs Input device found: CH Control Manager Device 2 Instance: -814---1-1668800 ProductName: CH Control Manager Device 2 Product: -61-000000876876 Type: Joystick. Subtype: Joystick that does not provide the minimum number of device objects for action mapping. Detected: 0 buttons, 4 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Joystick added to list Found joystick element: X Axis Smoother created: X Smoother x 0 Found joystick element: Y Axis Smoother created: Y Smoother y 4 Found joystick element: Y Rotation Smoother created: rY Smoother ry 16 Found joystick element: X Rotation Smoother created: rX Smoother rx 12 Found joystick element: Collection 0 - Joystick GUID_Unknown detected Using joystick elements: 0 buttons, 4 axes, 0 povs SoundManager: Starting... SoundManager: DirectSoundEnumerate DXMixer Primary Sound Driver : Starting... DXMixer Primary Sound Driver : Start succeeded DXMixer SB Audigy 2 ZS Audio [b800] : Starting... DXMixer SB Audigy 2 ZS Audio [b800] : Start succeeded SoundManager: DirectSoundCaptureEnumerate DXCapturer Primary Sound Capture Driver : Starting... DXCapturer Primary Sound Capture Driver : Start succeeded DXCapturer SB Audigy 2 ZS Audio [b800] : Starting... DXCapturer SB Audigy 2 ZS Audio [b800] : Start succeeded SoundManager: Start succeeded Sound Card Information: 4000 Minimum sample rate specifications that are supported by this device's hardware secondary sound buffers. 192000 Maximum sample rate specifications that are supported by this device's hardware secondary sound buffers. 64 Number of buffers that can be mixed in hardware. This member can be less than the sum of dwMaxHwMixingStaticBuffers and dwMaxHwMixingStreamingBuffers. Resource tradeoffs frequently occur. 64 Maximum number of static buffers. 64 Maximum number of streaming sound buffers. 62 Number of unallocated buffers. On WDM drivers, this includes dwFreeHw3DAllBuffers. 62 Number of unallocated static buffers. 62 Number of unallocated streaming buffers. 64 Maximum number of 3-D buffers. 64 Maximum number of static 3-D buffers. 64 Maximum number of streaming 3-D buffers. 62 Number of unallocated 3-D buffers. 62 Number of unallocated static 3-D buffers. 62 Number of unallocated streaming 3-D buffers. 0 Size, in bytes, of the amount of memory on the sound card that stores static sound buffers. 0 Size, in bytes, of the free memory on the sound card. 0 Size, in bytes, of the largest contiguous block of free memory on the sound card.

I have no idea what mobo is in this computer... it's an HP that I got retail and upgraded. I tried shutting down a lot of processes and it didn't help. I'll try unplugging USB stuff next.. after that the only thing I can think of to do is a clean Windows install.

Disabling autoprotect didn't help. I also tried setting my desktop to 1024x768 before starting LockOn, but that didn't help either.

I have Norton Systemworks and Internet Security 2005 running. Never had them interfere in a game before either. ::shrug:: I'll try disabling it. 15 minutes is generous. It's more like an hour.

I have a thread "Delay in Starting Game" which explains why I haven't enjoyed this experience so far. I've spent so much time trying to fix this that I haven't even had a chance to actually fly!

Catalyst 5.2 drivers for the graphics... and I'm pretty sure I have Creative's latest drivers for the Audigy2 ZS.

I did a reinstall and a manual activation and it didn't help.

I already tried copying the clean install back over it. Perhaps uninstall, then copy the clean on back, and then add the reg keys? I suppose Starforce would still be active.

Running LockOn.bat isn't helping matters... the only other thing I saw in that thread was to try reinstalling (without uninstalling) and use manual activation (I used auto on this install). Any other suggestions before I try that? I'd like to avoid a reactivation, because in the near future I'll be buying a new mobo and CPU, and probably a new video card (I'm moving towards 64bit and PCI Express). I have the registry key backed up.

I looked through several pages and couldn't find any... but I get the feeling I saw something like this before also. Strange that my sig didn't show... the specs are in it. Here they are in case it doesn't show for you: P4 3.0 GHz, 1.5 GB RAM, 9800XT, CH FS/FSP/PT/PP/TQ/Yoke, Aimsworth MFDs/ICP, X-Keys 20/58, Logitech LX700 keyboard/MX1000 laser mouse, TrackIR3 Pro

Guys, this is starting to get me pretty frustrated. After running the desktop shortcut for LockOn 1.1, it can take as many as 15 minutes before LockOn finally loads and I get to the main menu. Why is that the case? Is it something to do with activation? I don't see any windows popping up. If I put my mouse in the center of the screen, the cursor DOES change to the game's hourglass cursor. Please help me out here.. it's becoming one of those "bash your head against the desk" things. :confused: