Thread: Kitchen OEMs
View Single Post
  #97 (permalink)  
Old 02-20-2007, 05:49 AM
helmi_c's Avatar
helmi_c
Retired Staff
Offline
 
Join Date: Jan 2007
Posts: 128
Reputation: 769
helmi_c knows their stuffhelmi_c knows their stuffhelmi_c knows their stuffhelmi_c knows their stuffhelmi_c knows their stuffhelmi_c knows their stuffhelmi_c knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by schettj
Quote:
Originally Posted by master_shake
Quote:
Originally Posted by schettj
(Both of these have \Program Files\appname\ file paths hard coded
How do you tell if a program has that hardcoded in it ir not?
Trial and error - try building an OEM, build the rom with it, flash, test - if the app complains about something missing when launched, that's usually a sign. After you get the error, manually copy all the app files to \\Program Files\App (where app is the dirname it makes when installed via CAB) and relaunch it - if it works then you know it's hardcoded.
hmm... as far as I know profesional app should not/never make their app hardcode (except \Windows dll base) if so? what if we install it to Storage Card? the app will not work then, and that makes the app seems un-profesional dont u think?...

maybe the problem is registry value for it dependency or something like that....?
Reply With Quote