
HyperHacker
MemberContent Type
Profiles
Forums
Events
Everything posted by HyperHacker
-
All those memory optimizers do is allocate a bunch of memory, then free it, forcing Windows to move things to the page file and such to make room. If the OS is no good at memory management, that still won't make a huge difference. Also, it's pretty easy to get a huge uptime if you just hook the computer up, turn it on, and never actually use it.
-
Can't change window style
HyperHacker replied to HyperHacker's topic in Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
Thanks, I must have missed that. Another problem, though. After I change the style, the WS_EX_NOACTIVATE style no longer applies, even if I set it again after I change the style. Just like with the border, the style is set but the window can still be activated (though before changing the style, it can't, as is expected). It doesn't seem to make a difference whether I call SetWindowPos before or after re-applying the extended style. Also how do you reserve an area of the screen? Like wherever you place the taskbar, that area is excluded from the work area; a maximized window won't occupy that space. I want to reserve space like that, but not actually put a window in it. I know this can be done because if I terminate Explorer in Safe Mode (in normal mode it respawns) the space reserved for the taskbar is still reserved until I start Explorer again, and I can drag windows into it and see my desktop but if I maximize a window, they act like the taskbar was still there. [edit] Wow, reserving screen space is easier than I expected. RECT rect; SystemParametersInfo(SPI_GETWORKAREA,0,&rect,0); //modify the rect however SystemParametersInfo(SPI_SETWORKAREA,0,&rect,0); -
I'm having a strange problem with window styles. I create a window with the WS_CHILD, WS_POPUP and WS_VISIBLE styles using CreateWindowEx(), and it works fine. However, if I later add the WS_BORDER style using SetWindowLong(), nothing happens. Spy++ shows that it has the WS_BORDER style, but there is no border. Similarly, if I create it with the WS_BORDER style, a border is drawn, but it won't disappear if I remove the style. The window is completely erased and redrawn about once per second so I don't think it's a drawing problem.
-
Actually, that's the problem. Since I don't have the driver it's installed as a Standard 101-Key Keyboard. Windows just seems to be assuming that all keyboard multimedia keys do the same thing.
-
The one posted above. Though I'm not sure it actually works anymore, given that notice. And there doesn't seem to be any 'Login As' option. Maybe I'm using an old version...
-
I tried to use GmailFS a while ago to upload a file to my account, but I mistyped the password. Now every time I try to access it or its properties it still tries to log in with the same invalid password I gave it the first time. I searched through the registry and deleted all the keys but it's still remembering somehow. >_< How do I reset the password so I can enter the correct one?
-
I don't see why that second %1 is even there... o_O Try adding quotes around it. I'm not sure if you have to use \" or if just " will do.
-
If you don't want to waste CDs, just use CDRW. XP won't mind, it's just a matter of if the drive can read them (and most any will, except really old ones).
-
Have you changed any hardware, and have you tested what's in there? The hibernation process is very low-level and won't check to see if anything's changed or stopped working, which will usually throw it off and crash the system.
-
Forcibly uninstalling an antivirus may leave your system in an unstable condition, as they often use device drivers and such and get buried really deep in the system. If you have the option, just dump McAfee altogether.
-
Yay! I don't suppose I can change the default path? (When an app doesn't specify one, it starts in My Documents.)
-
If you mean the 'copying' animation at the top, those are AVI files in some DLL. You can replace them with whatever you want.
-
It won't run on 98 and probably not 2K; too many API calls are added in XP that it uses. However, ReactOS might be a solution to this. It's basically a total Windows clone project (that is, an unofficial version of Windows) that's designed to be compatible with all versions, so once they get around to uxtheme.dll, you should be able to use their version on Win98.
-
You answered yes to 8 of 20 questions. You are 40% addicted to Porn. There has been 21449 person(s) as addicted as you. That's it?
-
Hm, the only thing under Policies is explorer. And I'd rather not have to download a program just to change it.
-
The FPU may be built into the CPU but it is a separate circuit. In this case the OS would simply use standard x86 code to do floating-point math instead of having the FPU do it.
-
Why disable RPC, you can't install anything without it. I tried, it was a huge pain.
-
%* will pass all parameters instead of just the first one. Also, an interesting (and very annoying ) tidbit about XP's command line processor is that when you pass a filename pattern (*.*, *.bat, file?.exe etc) to any program, it will automatically be replaced with any filenames that match it. Lemme try to explain: -If you have a directory with the files bah.txt, buh.txt, foo.bar and program.exe in it, and you execute 'program.exe *.txt', it will act as if you executed 'program.exe bah.txt buh.txt'. -If you execute 'progam.exe foo.*' it will act as if you executed 'program.exe foo.bar'. -If you execute 'program.exe *.*' it will act as if you executed 'program.exe bah.txt buh.txt foo.bar program.exe'. -If you execute 'program.exe *.wtf' it will do as expected and simply execute 'program.exe *.wtf', because the pattern *.wtf does not match any files.
-
Have you tried Memtest86? Let it run overnight and it should determine if you have any RAM problems. Also, a more powerful power supply might help. I had an older computer which would corrupt memory at random causing all sorts of little problems (never bluescreened except due to video driver bugs, but things would behave oddly, occasionally simple math equations would give weird results, etc). I never did figure out exactly what the problem was but I could tell it was either the motherboard or CPU, and it only had a 100-watt power supply which I highly suspect may have caused some of these problems. An even older computer displayed the same symptoms, but much more severe (RAM would fail when hard disks were connected, to the point that the POST screen got corrupted), when its power supply failed (noticed the power LED was off ); I replaced it and it worked fine.
-
Oh sure, the memory cards are a buck for 30GB but the drive costs $10,000.
-
Ugh, I know what you mean. No matter how much I try to protect them my video games always end up getting stolen.
-
Those keys only seem to apply to Office, which I don't have. And with hardlinks, wouldn't that mean when I open the folder on the desktop it would be seen as Desktop\Whatever instead of its real path?