I just got XP 64 for my Athlon 64 system, and while the OS is sound, Litestep commands and such don't work. Namely Control pannel, and various other little links (I'll submit them as I find them). It'd also be nice to have LS take advantage of the native 64 bit code.
I know I'm asking a lot, but if people could offer a little support, I'll try and find and note changes that need to be made.
~DV
litestep.net development forums
litestep.com development forums
Also do a forum search here for "64 litestep" or something...
ate it because you don't know how to post you friggin n00b! :) Quote your links and you can use more than one.
It still begs the question has anyone managed to compile a 64 bit version yet, 'cause the 32 bit current build crashes my system alot, plus Control Pannel doesn't work (so I can't use it right now)... I miss my LS... :(
ahhhhhh quote the "links", gotcha ;) you friggin din0saur! :)
Dark: I think RabidCow was trying to get ls working on a 64... but idk where he is.
fract: Thanks, I hope he gets it working soon. I'm so ready to enjoy 64 bit but it just doesn't feel the same without litestep... ::Sigh::
Current status:
- LiteStep compiled for x64 is a LONG way off, because all the modules are 32-bit and you can't load them into a 64-bit process.
- 32-bit LiteStep works fine on x64, except it cannot access the 64-bit system32 directory.
There is an easy way to disable the redirection that causes this problem, but we need the redirection for modules to load correctly. So the trick is getting it enabled in all of the right places and none of the wrong ones.
- Omar's installer does not disable Explorer as shell correctly.
There is apparently a fix for this, though I have not yet tested it myself:
http://lsdev.org/forum_viewtopic.php?9.199
Even after changing the keys that selyb suggested in the other forum, the explorer shell is still trying to take over. I've tried numerous variations in editting the evarconfig with the different paths to explorer with no luck.
Inside and outside of Wow6432Node? I don't know which one is correct... (should only be for HKLM)
If you don't see HKLM/SOFTWARE/Wow6432Node, press ctrl-alt-esc and run regedit from there. (ie, get the 64-bit regedit)
neg... still doesn't work. and ctrl-alt-esc did nothing for me. I'm trying this on two machines. My personal computer and a Virtual Machine with a fresh install of x64. still not luck.
er, that should be ctrl-shift-esc...
So open up taskman and then open regedit? It's still 64-bit regedit.
That's the point. If you run regedit from litestep it'll be 32-bit regedit and you won't see Wow6432Node.
whats the status on this build?
while running on the 64 explorer shell, I couldn't locate the HKLM fodler at all.... I ran regedit from task manager and the start>run but neither show the HKLM root.....any ideas?
Are you logged in as an adminstrator?
Yes, my primary account is set up to be as such.
I'm a moron...can someone confirm or deny that HKLM stands for HKEY_LOCAL_MACHINE?
I thought it was a Dutch hairline.
I must confess that joke escapes me.
I believe Boreas is speaking of HKM which was an old airline...but I could be wrong.
KLM = airline, so HKLM = hairline. Actually... never mind.
I wonder what it would be like to vacation inside Brian's mind...
durr...which way did he go George...which way did he go?
from Russian-English dictionary:
George (n)
1. pilot
2. automatic pilot
Boreas is an aviator, am I right?
Ok with thoughts of the movie Airplane rushing through my head...this thread comes to a close.