Posted by member 31748 on 2003-05-10 03:46:05
I've been using Litestep for a while now and I've had issues with it and XP I thought would be fixed sooner or later but no one seems to notice it, and nothing's been done with each new Indiestep build. I got two problems:
1) The VWM is screwed. No matter which vwm module I use, it does the exact same thing (in fact most external vwm apps do this with XP as well). The problem is that maximised windows have the temperament of remaining sticky most of the time. They just follow me around whatever their sticky state is and whichever vwm module I use. What's up with this and why hasn't anyone fixed it? All the XP installs I've done have this prob.
2) Have you noticed the shutdown time? There's like a 20 second pause of no disk activity or anything (just waiting) during the message "Saving Settings...". This is not true when using explorer, the saving settings screen only takes less than half a second. So I thought this might just be M$ being a b*tch, doing this with any custom shell since it did this with the latest build of Geoshell as well. Then, one day, I went against my anti-$hareware morals and gave Aston a try. The saving settings screen took less than half a second, just like in explorer, so guess it can't be just coz of a custom shell. Has anyone had a look into this issue? Why does XP wait for like 20 seconds?
thx,
eXp
1) The VWM is screwed. No matter which vwm module I use, it does the exact same thing (in fact most external vwm apps do this with XP as well). The problem is that maximised windows have the temperament of remaining sticky most of the time. They just follow me around whatever their sticky state is and whichever vwm module I use. What's up with this and why hasn't anyone fixed it? All the XP installs I've done have this prob.
2) Have you noticed the shutdown time? There's like a 20 second pause of no disk activity or anything (just waiting) during the message "Saving Settings...". This is not true when using explorer, the saving settings screen only takes less than half a second. So I thought this might just be M$ being a b*tch, doing this with any custom shell since it did this with the latest build of Geoshell as well. Then, one day, I went against my anti-$hareware morals and gave Aston a try. The saving settings screen took less than half a second, just like in explorer, so guess it can't be just coz of a custom shell. Has anyone had a look into this issue? Why does XP wait for like 20 seconds?
thx,
eXp