Search Results
6/16/2025, 1:55:29 PM
>>105591793 (brace for the multipost)
>There were also a lot of COM servers that registered themselves via 8.3 name back then, too. I have a number of utilities from the 90s that I still use daily. As usual, it is a backcompat thing. But, to be completely honest, for the hoi polloi, it can go.
Fairs. I wouldn't consider doing that when dealing with an environment that depends on critical DOS/9X-era soft, either, but when you just occasionally fool around with these stuff - I guess ramping up a VM or an emulator like DOSBox/86box won't hurt. Depends on your needs, ofc.
Ya know, just came to my mind that since FSUtil does disable short-name genning either volume-level or system-wide (only have it set to the earlier), I guess I could workaround with a mounted virtual disk that will have it enabled as an "8.3zone" for the apps. Probly good-in-theory-yet-retarded-in-practice, but I guess it could work.
PS. Funnily, I actually set my 120 gig SSD drive up within the partition stage of Setup. Hence why I noticed the fact (along the reason why there was no Recovery partition created - disk space constraints?)
>There's more to UAC than just elevation. Another anon righteously said a thread or two back that people forget about the FS and registry virtualisation it offers.
Gonna stroke my own ego and admit that's me.
>Thankfully, this guy "disables" UAC "the right way" by not actually disabling it at all (which a lot of memescripts do, causing much mayhem among Dunning-Kruger sufferers), and just doing the RegEdit equivalent of whacking all the sliders up to the max.
"Slightly" above the sliders - ConsentPromptBehaviorUser set to 0 actually prohibits elevation for non-admin accs. Might be overkill but if you (and the apps) can handle it and follow the strictly-separated user/admin layout, I guess it werks.
(cont.)
>There were also a lot of COM servers that registered themselves via 8.3 name back then, too. I have a number of utilities from the 90s that I still use daily. As usual, it is a backcompat thing. But, to be completely honest, for the hoi polloi, it can go.
Fairs. I wouldn't consider doing that when dealing with an environment that depends on critical DOS/9X-era soft, either, but when you just occasionally fool around with these stuff - I guess ramping up a VM or an emulator like DOSBox/86box won't hurt. Depends on your needs, ofc.
Ya know, just came to my mind that since FSUtil does disable short-name genning either volume-level or system-wide (only have it set to the earlier), I guess I could workaround with a mounted virtual disk that will have it enabled as an "8.3zone" for the apps. Probly good-in-theory-yet-retarded-in-practice, but I guess it could work.
PS. Funnily, I actually set my 120 gig SSD drive up within the partition stage of Setup. Hence why I noticed the fact (along the reason why there was no Recovery partition created - disk space constraints?)
>There's more to UAC than just elevation. Another anon righteously said a thread or two back that people forget about the FS and registry virtualisation it offers.
Gonna stroke my own ego and admit that's me.
>Thankfully, this guy "disables" UAC "the right way" by not actually disabling it at all (which a lot of memescripts do, causing much mayhem among Dunning-Kruger sufferers), and just doing the RegEdit equivalent of whacking all the sliders up to the max.
"Slightly" above the sliders - ConsentPromptBehaviorUser set to 0 actually prohibits elevation for non-admin accs. Might be overkill but if you (and the apps) can handle it and follow the strictly-separated user/admin layout, I guess it werks.
(cont.)
Page 1