ANPres wrote:After update I got like, 4 error messages, "Cannot load kernel.." blah, blah, blah. Basically looks like whatever was supposed to be updated, didn't.
When this occurs during Inner Space patching, it usually means you have a process which has the Inner Space DLL's loaded into it. If you have exited a game prior, then it has not shutdown correctly. You can chase it if you like, or you can do a computer reboot to clear it. Patch before trying to load anything else under Inner Space.
ANPres wrote:But, Lax, I'm seeing just really weird stuff in the past few months.
If you mean from prior to the 28th August, then ok, but that means defining aroundabout when it started, and was it after a game patch, Windows patch, or a specific InnerSpace patch? The archive doesn't have a full list so this might be hard to test, but if you could recall a specific timeframe that would probably help.
If you mean after 28th August, then that was when the rewrite of the Inner Space loader began (well it actually began earlier, but there were a couple of patches in the dev builds between the initial push of 6195 on 13th Sep), so that at least would be more specific, and help to indicate that the loader is not quite there yet with SWG.
ANPres wrote:One of my hotswaps to, say, screen 16, is alt-cntl-num2. Won't even take it. I had to move it to alt-contrl-numdel.
The NumPad is a funny beast (and I'm sure you know this stuff). Not the least because NumLock changes the 2 key between NUMPAD2 and DOWN (i.e. the ARROW), so it can depend on the numlock state as to whether CTRL+ALT+NUMPAD2 will do anything.
Question is, does it work if you use InnerSpace build 6174 (which was live from June to Sep), or just not at all?
ANPres wrote:Like, I'll run 18 screens, for some reason, one of them won't load, (even after trying to force it..) I close out, restart and it will come up.
With your games not loading, is this a new thing too? If so, then again, can you say when that started?, How about grabbing a
compatibility diagnostic, as this would be the first place to start to look into this stuff, and see if there is anything obvious just lurking there.
One of the harder parts of this will always be that we wont be testing with 18 instances of the game, so if this is not reproducible with a lessor number, then we will be relying on you to provide some info. If it happens that the one that wont load actually hangs in the background, rather than a straight out refusal to load (which is probably a more fundamental issue), then it would probably help to get a Trace Diagnostic on the hung game.
ATEOTD, you can revert back to build 6174 if that was working for you. Currently the mouse issue for SWG has not been resolved at this time, so you wouldn't necessarily be missing out on anything by doing so.