bbgun;2264058 said:I'm trying to "crack" a program (don't judge me), and was told to place the patch in the "installation directory." Where can I find that directory on a typical Dell XP computer?
bbgun;2264241 said:Thanks. I notice there are 8 sub-folders in the i386 folder. Maybe I just need to place the patch in the main folder.
BrAinPaiNt;2264255 said:That will probably work.
However you could also copy the file and put it in the other ones as well. I doubt that would cause a problem.
bbgun;2264298 said:Some guy who's walking me through this told me I just needed to place the "configuration.dll" crack-patch in the program files folder, overwriting the old one. I did so, but the program wouldn't work when I tried to open it.
BrAinPaiNt;2264420 said:Make sure you have a copy of the file stored somewhere else.
Delete the DLL and/or file you placed in the programs file.
Reboot your puter.
Copy the program again and put it in the programs folder and see if it works there.
Not really sure what you are trying to crack, I take it that it is not the cd key or EULA or you would not even be far enough along to get to a program folder...unless you are going into dos before windows OS loads up.
bbgun;2264543 said:You seem to have experience doing this. I'll send you a more specific PM later.
BrAinPaiNt;2264604 said:Probably be better off finding a tech forum.
Kilyin;2264668 said:What program are you trying to apply this 'patch' to specifically?
bbgun;2264681 said:BlazeDTV3.5. My trial version expired, and I need something to replace my unreliable, bug-filled Pinnacle PCTV.
Kilyin;2264692 said:The program directory would probably be C:\Program Files\BlazeDTV or something similar. If you right click the shortcut on your desktop or under the start menu itself and go to properties, the path listed there should confirm the location of the program directory, which is where you'd place said 'patch'.
C:\I386 is actually a cache folder for Windows system files and has nothing to do with applications installed on your computer.
Kilyin;2264953 said:Could be a bunk crack... did it come with a readme?
Kilyin;2265680 said:Looks like you did everything correctly. It might not necessarily be a fake crack, but it could just be a poorly coded one that doesn't work.