Related
Apologies if this has been covered before, found these settings on another website (http://smartmobileassets.com/cgi-bin/Blah/Blah.pl?b=winmobile,m=1132411511)
Have they been tried and do they make any difference?
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\CacheSize=0x1000(4096)
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\EnableCache=0x1(1)
HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt\ReplStoreCacheSize=0x1000(4096)
Yes they work!
Yes they work beautiful on my Jasjar, the device is noticeable faster in all the applications.
Thank you!
Rodrigo Gonzalez
Cache settings, hum... how safe is this?? I take the chance and test them
Morituri said:
Apologies if this has been covered before, found these settings on another website (http://smartmobileassets.com/cgi-bin/Blah/Blah.pl?b=winmobile,m=1132411511)
Have they been tried and do they make any difference?
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\CacheSize=0x1000(4096)
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\EnableCache=0x1(1)
HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt\ReplStoreCacheSize=0x1000(4096)
Click to expand...
Click to collapse
hi. please could you tell me is i need to insert the full value "0x1000(4096)" or only one of them? thank you,
Just one, one is the Hex Value the other is the decimal
Morituri said:
Just one, one is the Hex Value the other is the decimal
Click to expand...
Click to collapse
so for ex in hex 0x1000
sorry but registry is like crystal...
Just one, one is the Hex Value the other is the decimal
Yes, "0x1000" in Hex is identical to "4096" in decimal. Put whichever one you want into the relevant registry entry.
I've messed about with these registry settings too, but in all honesty I haven't noticed any difference in performance....
sub69 said:
but in all honesty I haven't noticed any difference in performance....
Click to expand...
Click to collapse
me too...
But as darkdestroyer says in the other sites forum...
Yes i've done this since it was first released on Aximsite by another member. At first I had 8 mb allocated, but i guess 4 is the best number. The PDA right after a soft reboot is still the same speed, but after you have all of the shortcut's/programs run once, they will be put into ram and the following run's of those same programs/shortcuts will be much much faster. This is indeed a great find and should be standard with WM5
Click to expand...
Click to collapse
No changes in the performance of the device.
The only change is battery draining faster than the original settings.
I've done these changes before and had to reflash the ROM again to my device.
I don't see any need to make these changes, and I don't advise any one to do them.
Regards,
These registry settings have been reported to increase performance by many users on different forums, some using the Dell Axim x51v ,BA users and even some Universal users and are even incorporated into tweaks2k2. My advice is to try them for yourself and make sure the changes are actually being applied after a soft reset and then perform some tasks on your device (see the post by Carnivor) and then make your own judgement. No one so far has reported any negative impact apart from a small reduction in program memory. The changes can always be reversed if needed.
Carnivor said:
But as darkdestroyer says in the other sites forum...
Yes i've done this since it was first released on Aximsite by another member. At first I had 8 mb allocated, but i guess 4 is the best number. The PDA right after a soft reboot is still the same speed, but after you have all of the shortcut's/programs run once, they will be put into ram and the following run's of those same programs/shortcuts will be much much faster. This is indeed a great find and should be standard with WM5
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Erm... so is this registry tweak adding cache memory to the system for running applications then? So that .exes or .dlls that are loaded when a program is run are available more quickly to the system next time they're needed?
If so (and I can't quite believe that this could be the case ), are we now recommending that we allow programs to stay resident in memory to speed up the machine?
... much like the standard PocketPC "Minimise, not close" behaviour that people seem to hate so much?
LMFAO if so! (and please tell me I'm wrong if not! )
SiliconS,
You are absolutely wright.
The proof is that after making the registery editing the application when opened for the first time it does not open on a faster way than the original settings, but when you open it for the second time it opens faster that the first time.
The appications remain opened in the phone memory and reduces the devices memory and the battery life as well.
Microsoft's WM5 development team must be LTFAO when they read stuff like this. People spend hours complaining and looking for ways of forcing the system to properly close apps using MagicButton or PocketPlus, and complain when their WM5 machine runs slow.
Then someone comes along offering a way of speeding things up by caching programs and files in memory!!
Am I the only person who thinks this is utterly bizarre?
Oh, man. MS must be laughing at us. :shock:
(No offence intended to anybody - I'm just amused by this. )
So, if you are running something like GSPocketMagic, Magic Button, etc, which actually close applications properly, all you are doing is reducing the amount of memory available to run programs with no gain whatsoever?
Well I made the changes and found no improvement in speed, but it was worth a try. In the light of what has been said, I'd like to change back the settings, but can't remember what they were!!!!!
Can someone post up the original values please
Here they are:
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\CacheSize=0
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\EnableCache=1
HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt\ReplStoreCacheSize=0
Many thanks - all sorted
Guys, these registry hacks work! If you haven't been able to get them to work you may have missed a step or two.
First of all, Windows Mobile 5 already holds running information in the RAM, so these tweaks do not truly change that but they do enhance it to make the WM5 device runs MUCH better.
I've have had a TON of people comment and e-mail me about these changes both on my site and many others about how well these tweaks work. In fact, I don't think that the developer of Tweaks2k2 would include that in his latest version if it didn't work.
Couple things; you have to either cycle the power on your WM5 device or do a soft reset from a software app only! Cycling the power will write anything in RAM to ROM, in this case the registry settings you have just changed. If cycling does not work you should soft reset your device using a software app. I think there are a couple free apps to do that but you can also use SPB's Pocket Plus or others. If you just hit the reset button on the back after making the changes it soft resets right away without writing RAM content to ROM.
You can check this by looking at your registry settings after a soft reset to see if the changes took.
I have still noticed that sometime after a reset my device will still run slowly but it isn't because of these changes. In fact, most of the time it is perfectly fine and MUCH better than it was before the changes. MUCH!
Be sure to also turn off error reporting and do the activesync hack to keep those from draining battery and you should do well.
Again, many have made these changes and seen a very significant improvement in performance.
Hi wondering if someone can help.
In the latest rom update from O2 if you install the active UI it will give you a battery today plugin which is quite handy.
Now my question we all know the ActiveUI is horrible will slow down the exec and take up to much space. Is there anyway of stripping out this battery today plugin form the ActiveUI and creating a cab file so it will just install this part. I think the file that is needed from the ActiveUI is BatteryNFO.
Many Thanks
Scott
Wow 50 views and still no one got an answer????
Got to say I'd love this too. I've tried other battery monitors, and none are as good as that one.
Ok i have been looking in to this since i posted and have extracted the signed_UNI_o2AUI4_build88.cab file to my home machine. From What i can see there are 7 files that could be related to this 4 of which start with batter~1.029 and so on the other 3 start with power_~1.070. is there anyway of telling what these files are actually for.
Im no expert at this but surely it can be done as i have seen people have ripped the connection settings from this cab file before so surely the same sort of thing can be done with this.
Cheers
Scott
i agree...looks quite nice this battery plug-in...hope sum1 finds a way of getting it as a cab file soon
Still looking in to this and not going to let it beat me to.
Has anybody ever used this software before.
http://www.pocketgear.com/software_detail.asp?id=12093
MagicCab PocketPC CAB extractor 0.63
It looks like it is going to do what i need and be able to strip out the battery today plugin from the cab and even tell us what reg settings we need to enter to if i am reading it right but before i commit myself to the $10.95 has anyone ever used it before to clarify that it will do what i need it to do.
If you want something more professional use WCE CAB Manager.
Why not use Batti ?
It gives you just as much information, doesn't take up valuable Today space or slow down your machine, is visible in every application not just Today, and runs in just 20K. And it's free
Right
So far with the advice given to me by ibendlin about wince cab manager and after several hard resets (trial and error thank god for spbpocket backup lol) i have manged to get half way there. But i am having a problem getting the skins to work
As you can see i have manged to sort the today plugin but im having problems getting the skins working even after a soft reset.
Maybe someone can offer some advice i will gladly forward the cab that i have created so far if anyone can offer some suggestions.
Ineedtoys: So far i have manged to get this down to 14kb as for the space on the today screen user preference really, but thank you for your advice on batti.
Anyway off to bed will work on this some more tomorrow
OK, if you dont activate the ActiveUI thing in programs then you can have life without it. To get it to go away now that its on goto \windows\startup and delete the ActiveUI file in there. You cant seem to unistall the program. I just avoid the icon like the pluage.
There are more complex ways of getting what your looking for, but this one is simple and effective
JAmes
ps. then soft reset
Hi James
Tis true what you are saying and this way will work but unfortunatly you will also get about 10mb worth of extra programs installed from the activeUI which take up the oh so precious Device storage space where the actual battery bar it's self only takes up around 14kb
But thanks anyway
yeah but the newer people to the scene might not like playing about with things. I've only just got use to playing about with stuff and up untill now I've been using this solution.
Now i've had the phone a wee while i'm happy to start going for corporate mode but was easier not to when i was just getting use to the whole PDA type stuff
JAmes
I know what you mean we all had to start somewhere right lol.
I stopped using the the personal install about a month after i had my exec it was only through advice from these forums that i actually found out how much space the activeUI took up and also how much it slowed it down.
I use this one:
it shows 2 lines: one for main Battery status and one for Backup Battery status (no more exists in WM5); it works well
tried this one but I still think the one in the latest rom release from O2 looks sharper/prettier....
Yeah i'm planning on giving up the basic mode soon.
let me know how you get on, as I too like this battery meter.
JAmes
Fellas
I Have done it, Sort of. Still a few bugs but i don't think i will be able to sort these limited knowledge and already about 10 hard reset's.
I have been using now for around 8 or 9 hours now and all seems to be fine after the install no memory loss or anything.
Works well in True VGA to.
congrats m8..any chance of u posting the cab file here?
hiya scotjen,
dont mind you posting it out here??
thanks...
damn, I still have a Champions League game against Arsenal later.
got to get back to training soon
Well done.
What bugs are you still experiencing. Maybe someone could advise you further?
Hi,
My Hermes cannot anymore find the memory card: "Not installed".
How can I fix this?
The problem started when I interrupted a syncronisation to Win Media Player 11.
I have tried to soft reset the Hermes both without and with the memory card but whitout results.
?
Because the time in Sweden is almost two in the morning I will go to bed now but will check any responses as soon as I can.
/Danne
Have a read of this thread http://forum.xda-developers.com/showthread.php?t=294324. There are various fixes for this problem.
Ok, but how?
Hi,
Thanks for the reply and with a solution! I am not shure I have the exactly same problem, the Hermes doesn´t even find a directory folder for the memory card, but I want to try the solution proposed in the thread you sent.
But I don´t know WHERE I should do the hack and how, just write the below?
Is it here somewhere? "Settings / System-flap / ?
THE SOLUTION
"After working at the issue for a while, here is the end results:
Do the following reg. hack (numbers are in DECIMAL!
hex equiv. is 0x2004):
[HKLM\System\StorageManager]
"PNPUnloadDelay" = dword:8196
[HKLM\System\StorageManager]
"PNPWaitIODelay" = dword:8196"
/Danne
You need to download a registry editor (eg: PHM RegEdit) to make these changes. Search the forum... cabs have been posted many times... or google it!
Hope this helps!
OK
I will try that, but not today, it seems as that may take a while to fix.
Thanks, both of you!
/Danne
actually, once you get the registry editor, it takes only a couple of minutes...
Hmm... my experice is that that nothing EVER take only a couple of minutes when it comes to computers
Is it the memory card that needs to be fixed or, is it the memory card specifically in connection with my TyTN (Hermes) only? I´m thinking about selling it and need to know if the buyer needs to fix this first.
I already ordered a larger Kingston memory - I noticed that people in the other thread seemd to think they were more stable, but I don´t know who to trust. I have gotten a lot of help from this forum and it is great (!), when I learn more I hope to give some back. But I know companies pays people to sit all day and recommend products in forums like these .
/Danne
so i actually found a copy of Retina WiFi scanner, and loaded it up on my HTC wiz (8125). But when I went to start it, it came back saying that it could not initiate the drivers, and that to turn my wifi card on...
Like I didn't already do that...
Anyone else come up with that error message, and is there any known way around it?
retina device driver;
hallo, i have the same problem. if you have found a sollution let me know
TYTN II UK
nope, no solutions. I actually abandoned the project cause i could find no one smarter then who actually knew what they were doing
The most I could come up with, however, was that for those that did get it to work, it usually took a long time for it to get anywhere, and by the time it did get anywhere their battery life was near shot.
I can send you the application if you like.
boe_dye said:
nope, no solutions. I actually abandoned the project cause i could find no one smarter then who actually knew what they were doing
The most I could come up with, however, was that for those that did get it to work, it usually took a long time for it to get anywhere, and by the time it did get anywhere their battery life was near shot.
I can send you the application if you like.
Click to expand...
Click to collapse
can you send me the file? pm me the link on rapidshare or something
weell....
well, apparently I misspoke. I thought i had that program stored away on my second harddrive, but apparently i do not. As it is, i don't have it anywhere except on my pocket pc and that is as an application.
however, i do remember reading somewhere that there is a program that can actually extract the .cab from the ppc in case of something like what has happened to me, happens. So i will research that and see if i can come up with something.
Again, I am really sorry, and rest assured if i did have it, it would have been up on rapishare that very day...
as it is, like most things, i am going to have to do it the hardway...
If in fact you do want to continue looking for it, i cannot remember if i found via torrent, or some russian site. those russian sites have EVERYTHING. Although I would suggest going through google to translate them. Unless of course you can read russian then kudo's to you.
Either way, I will work on seeing if i can extract the .cab from my phone.
stay tuned!
"Retina Wifi" is available for free from here -
http://www.eeye.com/html/downloads/index.html
You just have to register and they email you a download link. I shall have a play (although I shall be using a Hermes rather than my Wizard and probably won't come back to say if it works due to lazyness).
Hope that helps
that's new...
when i was there last, they said that they no longer supported the project. Unless this is a different think then what we were originally talking about.
the version that i was referring to, had a neat little brute force wep cracker. i read some pro's and con's to it and thought that it would be cool just to have.
but hey, register, and then share your find if it's worthwhile!
like i started to say earlier it has been a while since i played with my HTC wizard, and a lot of this is more or less a vaguery for me.
(yes i just made that word up)
boe_dye said:
well, apparently I misspoke. I thought i had that program stored away on my second harddrive, but apparently i do not. As it is, i don't have it anywhere except on my pocket pc and that is as an application.
however, i do remember reading somewhere that there is a program that can actually extract the .cab from the ppc in case of something like what has happened to me, happens. So i will research that and see if i can come up with something.
Again, I am really sorry, and rest assured if i did have it, it would have been up on rapishare that very day...
as it is, like most things, i am going to have to do it the hardway...
If in fact you do want to continue looking for it, i cannot remember if i found via torrent, or some russian site. those russian sites have EVERYTHING. Although I would suggest going through google to translate them. Unless of course you can read russian then kudo's to you.
Either way, I will work on seeing if i can extract the .cab from my phone.
stay tuned!
Click to expand...
Click to collapse
the only way of extracting an installed app as a cab from a ppc, that i know of, is sk schema or sk tracker, cant remember which but the software from sk has to be installed BEFORE you install the app
, so i doubt that will be of use to you.
hmmm...
yes, those names do sound familiar...
and yeah, installing it before hand might put a damper on things.
....
hmm i just had a thought, i wonder if i stored it as a backup on my sd card. as it is right i basically use my ppc for "war driving" (that is driving around in the car sniffing for wifi signals, courtesy of wififofum, for those that don't know) and as a glorified mp3 player for my truck (conduits player is great... just as a fyi)... however all my songs on my phone are all stored on a 2 gig micro sd card...
but i don't remember if i erased my backups to make room for more songs...
hold on all! don't close the thread yet there still may be hope!
do u still want the program ? let me know and I'll email you the install file.. I get the same error with the drivers on my qtek 9100. Let me know if you can get it to work.
i'm not 100% sure, but i remember seeing somewhere (years ago) that this program only works with compactflash wifi cards, and not internal ones. this could possibly be the issue about the driver thing. any other similar programs available for wep / wpa cracking?
bump... would love to see this app (or one like it work)
Put simply, i used OEMizer 1.3.9 to create a package out of SU2U v1.2.1 and, like many CABs, it didn't recognize the directories.
So, i added the files manually and edited them to point toward their correct directories. I did this, at least, 6 times.
The problem here is that OEMizer "insists" that i'm duplicating files. Well, i am but they're clearly shown to be in different directories. It's obvious that OEMizer doesn't know how to differentiate directories with duplicate name files (even when told).
Does anyone know how to work around this problem? I know Naigaman did something to get around the problem but trying to contact one of these guys is like trying to get a private meeting with the president so i can't ask him directly.
Anyone? Help.
What files do you have duplicated? I assume the clock.
Doesn't OEMizer put all the files in the same directory for an OEM package?
If so, then there can't be 2 files with the same name in the same directory.
If the files are identical, then delete one and use initflashfiles.txt to copy it to the two destinations.
If they are different files, but have the same name, then rename one, and use initflashfiles.txt to rename (to the original name) at the same time it gets copied.
joemanb said:
Doesn't OEMizer put all the files in the same directory for an OEM package?
If so, then there can't be 2 files with the same name in the same directory.
If the files are identical, then delete one and use initflashfiles.txt to copy it to the two destinations.
If they are different files, but have the same name, then rename one, and use initflashfiles.txt to rename (to the original name) at the same time it gets copied.
Click to expand...
Click to collapse
That can't be right because Naigaman did it with Slide2Unlock v1.18 on one of the kitchens and there are gfx directories in his and something had to make those directories. Besides, why would there be an "edit" to edit the file's directory markers if it put all the files in the same place. That would be like putting a "do nothing" button there just for looks.
Yes (replying to the message above this one), i think they're the clock files but i do know they go in different directories and the CAB file had them classed in a different directory. I also noticed that "packages creator 5.4" classifies them as "duplicates". However, unless people code without ever using a similar file in a sub directory (which this is the case) then i would classify this as a flaw in the program....unless there's some hidden checkbox i've missed that tells the program not to see these files as dupes.
However, i believe this to be some sort of flaw in the software where reading the cab's %insertdirectorhere% factor and not being able to translate it. I don't know why OEMizer can't do it unless the code was based on the same program and it's just an inherent flaw.
Directory("\Windows\Start Menu\Programs\S2U2\"):-File("S2U2.lnk","\Windows\S2U2.lnk")
Directory("\Windows\Start Menu\Programs\"):-File("Slide2View.lnk","\Windows\Slide2View.lnk")
Directory("\Windows\Start Menu\Programs\S2U2\"):-File("iLock2.lnk","\Windows\iLock2.lnk")
Directory("\Windows\Startup\"):-File("iLock2.lnk","\Windows\iLock2.lnk")
Directory("\Windows\gfx\clock"):-File("0.png","\Windows\s2u_0.png")
Directory("\Windows\gfx\clock"):-File("1.png","\Windows\s2u_1.png")
Directory("\Windows\gfx\clock"):-File("2.png","\Windows\s2u_2.png")
Directory("\Windows\gfx\clock"):-File("6.png","\Windows\s2u_6.png")
Directory("\Windows\gfx\clock"):-File("7.png","\Windows\s2u_7.png")
Directory("\Windows\gfx\clock"):-File("8.png","\Windows\s2u_8.png")
Directory("\Windows\gfx\clock"):-File("9.png","\Windows\s2u_9.png")
Directory("\Windows\gfx\clock"):-File("a.png","\Windows\s2u_a.png")
Directory("\Windows\gfx\clock"):-File("c.png","\Windows\s2u_c.png")
Directory("\Windows\gfx\clock"):-File("m.png","\Windows\s2u_m.png")
Directory("\Windows\gfx\clock"):-File("p.png","\Windows\s2u_p.png")
Directory("\Windows\gfx\clock"):-File("s.png","\Windows\s2u_s.png")
Directory("\Windows\gfx\clock"):-File("3.png","\Windows\s2u_3.png")
Directory("\Windows\gfx\clock"):-File("4.png","\Windows\s2u_4.png")
Directory("\Windows\gfx\clock"):-File("5.png","\Windows\s2u_5.png")
Directory("\Windows\gfx\clockA"):-File("ch4.png","\Windows\ch4.png")
Directory("\Windows\gfx\clockA"):-File("ch5.png","\Windows\ch5.png")
Directory("\Windows\gfx\clockA"):-File("ch6.png","\Windows\ch6.png")
Directory("\Windows\gfx\clockA"):-File("ch7.png","\Windows\ch7.png")
Directory("\Windows\gfx\clockA"):-File("ch8.png","\Windows\ch8.png")
Directory("\Windows\gfx\clockA"):-File("ch9.png","\Windows\ch9.png")
Directory("\Windows\gfx\clockA"):-File("ch10.png","\Windows\ch10.png")
Directory("\Windows\gfx\clockA"):-File("ch11.png","\Windows\ch11.png")
Directory("\Windows\gfx\clockA"):-File("ch12.png","\Windows\ch12.png")
Directory("\Windows\gfx\clockA"):-File("ch13.png","\Windows\ch13.png")
Directory("\Windows\gfx\clockA"):-File("ch14.png","\Windows\ch14.png")
Directory("\Windows\gfx\clockA"):-File("cm0.png","\Windows\cm0.png")
Directory("\Windows\gfx\clockA"):-File("cm1.png","\Windows\cm1.png")
Directory("\Windows\gfx\clockA"):-File("cm2.png","\Windows\cm2.png")
Directory("\Windows\gfx\clockA"):-File("cm3.png","\Windows\cm3.png")
Directory("\Windows\gfx\clockA"):-File("cm4.png","\Windows\cm4.png")
Directory("\Windows\gfx\clockA"):-File("cm5.png","\Windows\cm5.png")
Directory("\Windows\gfx\clockA"):-File("cm6.png","\Windows\cm6.png")
Directory("\Windows\gfx\clockA"):-File("cm7.png","\Windows\cm7.png")
Directory("\Windows\gfx\clockA"):-File("cm8.png","\Windows\cm8.png")
Directory("\Windows\gfx\clockA"):-File("cm9.png","\Windows\cm9.png")
Directory("\Windows\gfx\clockA"):-File("cm10.png","\Windows\cm10.png")
Directory("\Windows\gfx\clockA"):-File("cm11.png","\Windows\cm11.png")
Directory("\Windows\gfx\clockA"):-File("cm12.png","\Windows\cm12.png")
Directory("\Windows\gfx\clockA"):-File("cm13.png","\Windows\cm13.png")
Directory("\Windows\gfx\clockA"):-File("cm14.png","\Windows\cm14.png")
Directory("\Windows\gfx\clockA"):-File("cp.png","\Windows\cp.png")
Directory("\Windows\gfx\clockA"):-File("ca.png","\Windows\ca.png")
Directory("\Windows\gfx\clockA"):-File("cc.png","\Windows\cc.png")
Directory("\Windows\gfx\clockA"):-File("ch0.png","\Windows\ch0.png")
Directory("\Windows\gfx\clockA"):-File("ch1.png","\Windows\ch1.png")
Directory("\Windows\gfx\clockA"):-File("ch2.png","\Windows\ch2.png")
Directory("\Windows\gfx\clockA"):-File("ch3.png","\Windows\ch3.png")
Directory("\Windows\gfx"):-File("stbg.png","\Windows\stbg.png")
Directory("\Windows\gfx"):-File("stbutton.png","\Windows\stbutton.png")
Directory("\Windows\gfx"):-File("stbuttonL.png","\Windows\stbuttonL.png")
Directory("\Windows\gfx"):-File("stlrL.png","\Windows\stlrL.png")
Directory("\Windows\gfx"):-File("stonoff.png","\Windows\stonoff.png")
Directory("\Windows\gfx"):-File("stsystem.png","\Windows\stsystem.png")
Directory("\Windows\gfx"):-File("sttopbar.png","\Windows\sttopbar.png")
Directory("\Windows\gfx"):-File("stvtopbar.png","\Windows\stvtopbar.png")
Directory("\Windows\gfx"):-File("subbutton.png","\Windows\subbutton1.png")
Directory("\Windows\gfx"):-File("system.png","\Windows\system.png")
Directory("\Windows\gfx"):-File("topbar.png","\Windows\topbar.png")
Directory("\Windows\gfx"):-File("unknown.png","\Windows\unknown.png")
Directory("\Windows\gfx"):-File("vtopbar.png","\Windows\vtopbar.png")
Directory("\Windows\gfx"):-File("wallpaper.gif","\Windows\wallpaper.gif")
Directory("\Windows\gfx"):-File("wallpaperL.gif","\Windows\wallpaperL.gif")
Directory("\Windows\gfx"):-File("wallpaper.jpg","\Windows\wallpaper.jpg")
Directory("\Windows\gfx"):-File("wallpaperL.jpg","\Windows\wallpaperL.jpg")
Directory("\Windows\gfx"):-File("arrows.png","\Windows\arrows.png")
Directory("\Windows\gfx"):-File("notice.png","\Windows\notice.png")
Directory("\Windows\gfx"):-File("redcircle.png","\Windows\redcircle.png")
Directory("\Windows\gfx"):-File("s2ans.png","\Windows\s2ans.png")
Directory("\Windows\gfx"):-File("buttons.png","\Windows\s2u2_buttons.png")
Directory("\Windows\gfx"):-File("slide.png","\Windows\slide.png")
Directory("\Windows\gfx"):-File("vcbar.png","\Windows\vcbar.png")
Directory("\Windows\gfx"):-File("vcbg.png","\Windows\vcbg.png")
Directory("\Windows\gfx"):-File("vcbutton.png","\Windows\vcbutton.png")
Directory("\Windows\gfx"):-File("volume.png","\Windows\volume.png")
Directory("\Windows\gfx"):-File("slideanis.png","\Windows\slideanis.png")
Directory("\Windows\gfx\weather"):-File("10.png","\Windows\s2uW_10.png")
Directory("\Windows\gfx\weather"):-File("11.png","\Windows\s2uW_11.png")
Directory("\Windows\gfx\weather"):-File("12.png","\Windows\s2uW_12.png")
Directory("\Windows\gfx\weather"):-File("13.png","\Windows\s2uW_13.png")
Directory("\Windows\gfx\weather"):-File("14.png","\Windows\s2uW_14.png")
Directory("\Windows\gfx\weather"):-File("15.png","\Windows\s2uW_15.png")
Directory("\Windows\gfx\weather"):-File("16.png","\Windows\s2uW_16.png")
Directory("\Windows\gfx\weather"):-File("19.png","\Windows\s2uW_19.png")
Directory("\Windows\gfx\weather"):-File("20.png","\Windows\s2uW_20.png")
Directory("\Windows\gfx\weather"):-File("21.png","\Windows\s2uW_21.png")
Directory("\Windows\gfx\weather"):-File("22.png","\Windows\s2uW_22.png")
Directory("\Windows\gfx\weather"):-File("23.png","\Windows\s2uW_23.png")
Directory("\Windows\gfx\weather"):-File("25.png","\Windows\s2uW_25.png")
Directory("\Windows\gfx\weather"):-File("26.png","\Windows\s2uW_26.png")
Directory("\Windows\gfx\weather"):-File("27.png","\Windows\s2uW_27.png")
Directory("\Windows\gfx\weather"):-File("28.png","\Windows\s2uW_28.png")
Directory("\Windows\gfx\weather"):-File("29.png","\Windows\s2uW_29.png")
Directory("\Windows\gfx\weather"):-File("30.png","\Windows\s2uW_30.png")
Directory("\Windows\gfx\weather"):-File("31.png","\Windows\s2uW_31.png")
Directory("\Windows\gfx\weather"):-File("32.png","\Windows\s2uW_32.png")
Directory("\Windows\gfx\weather"):-File("34.png","\Windows\s2uW_34.png")
Directory("\Windows\gfx\weather"):-File("36.png","\Windows\s2uW_36.png")
Directory("\Windows\gfx\weather"):-File("37.png","\Windows\s2uW_37.png")
Directory("\Windows\gfx\weather"):-File("43.png","\Windows\s2uW_43.png")
Directory("\Windows\gfx\weather"):-File("45.png","\Windows\s2uW_45.png")
Directory("\Windows\gfx\weather"):-File("46.png","\Windows\s2uW_46.png")
Directory("\Windows\gfx\weather"):-File("47.png","\Windows\s2uW_47.png")
Directory("\Windows\gfx\weather"):-File("weather.png","\Windows\weather.png")
Directory("\Windows\gfx\weather"):-File("0.png","\Windows\s2uW_0.png")
Directory("\Windows\gfx\weather"):-File("1.png","\Windows\s2uW_1.png")
Directory("\Windows\gfx\weather"):-File("3.png","\Windows\s2uW_3.png")
Directory("\Windows\gfx\weather"):-File("5.png","\Windows\s2uW_5.png")
Directory("\Windows\gfx\weather"):-File("6.png","\Windows\s2uW_6.png")
Directory("\Windows\gfx\weather"):-File("7.png","\Windows\s2uW_7.png")
Directory("\Windows\gfx\weather"):-File("8.png","\Windows\s2uW_8.png")
Directory("\Windows\gfx\weather"):-File("9.png","\Windows\s2uW_9.png")
Directory("\Windows\gfx"):-File("pbackward.png","\Windows\pbackward.png")
Directory("\Windows\gfx"):-File("pbarbuttonpng","\Windows\pbarbutton.png")
Directory("\Windows\gfx"):-File("pbaroff.png","\Windows\pbaroff.png")
Directory("\Windows\gfx"):-File("pbaron.png","\Windows\pbaron.png")
Directory("\Windows\gfx"):-File("pforward.png","\Windows\pforward.png")
Directory("\Windows\gfx"):-File("ppause.png","\Windows\ppause.png")
Directory("\Windows\gfx"):-File("pplay.png","\Windows\pplay.png")
Directory("\Windows\gfx"):-File("ppressed.png","\Windows\ppressed.png")
Directory("\Windows\gfx"):-File("pvbackward.png","\Windows\pvbackward.png")
Directory("\Windows\gfx"):-File("pvbarbutton.png","\Windows\pvbarbutton.png")
Directory("\Windows\gfx"):-File("pvforward.png","\Windows\pvforward.png")
Directory("\Windows\gfx"):-File("pvpause.png","\Windows\pvpause.png")
Directory("\Windows\gfx"):-File("pvplay.png","\Windows\pvplay.png")
Directory("\Windows\gfx"):-File("pvpressed.png","\Windows\pvpressed.png")
Directory("\Application Data\AppToDate"):-File("S2U2SettingsPlus.xml","\Windows\S2U2SettingsPlus.xml")
Directory("\Windows\Start Menu\Programs\S2U2"):-File("S2U2 Wave Editor.exe","\Windows\S2U2 Wave Editor.exe")
Naigman must have changed the filenames
So, i added the files manually and edited them to point toward their correct directories. I did this, at least, 6 times.
Click to expand...
Click to collapse
So why do you need to use OEMizer now that you're doing manual editing, just finish the package. OEMizer doesn't do any special magic that's needed to make your package work in a kitchen.
That can't be right because Naigaman did it with Slide2Unlock v1.18 on one of the kitchens and there are gfx directories in his and something had to make those directories. Besides, why would there be an "edit" to edit the file's directory markers if it put all the files in the same place. That would be like putting a "do nothing" button there just for looks.
Click to expand...
Click to collapse
When your ROM boots is when the files are copied from the windows folder to the paths in intflashfiles.txt. All the files of your ROM originate in the Windows folder after the device boots! In your example, iLock2.lnk is copied from the windows folder to two different locations. THAT file (iLock2.lnk) is probably contained in the cab twice thus you get a dupe error WHEN OEMizer TRIES TO COPY THE SAME FILE TO THE OEM PACKAGE TWICE. When I asked "Doesn't OEMizer put all the files in the same directory for an OEM package?" it was rhetorical.... Watch my lips...
"an OEM package has ALL FILES IN THE SAME FOLDER!!!"
Also, all the files in a cooked ROM are in the same folder, the Windows folder...thus, THERE CAN BE NO DUPE FILENAMES, not only in the OEM package, but also in THE ENTIRE ROM.
However, i believe this to be some sort of flaw in the software where reading the cab's %insertdirectorhere% factor and not being able to translate it. I don't know why OEMizer can't do it unless the code was based on the same program and it's just an inherent flaw.
Click to expand...
Click to collapse
OEMizer is a tool TO HELP YOU BUILD AN OEM PACKAGE (most people do it by hand)! Its not perfect and most of the time you have to edit a line or two in the intiflashfiles.txt and/or rename files (most people don't bother removing the 'generated by' remarks, but that doesn't mean the file hasn't been edited) You have to know how an OEM package works. I don't think you do, because you didn't even try my solution, anyone who knows how and OEM package is put together would look at it and say "Ah yes I see". What you need to do is create a few packages manually to increase your understanding of how to put together a package. The software isn't helping in this regard.
When you come asking for help and then reject a workable solution because you're 'so dang smart', well, it just sort of irks me.
Why do I even bother trying to help...
BTW did you bother reading the OEMizer help file...Here are a few entries that indicate that the files need to be manually edited:
When a cab file is chosen to be imported, OEMizer will look for the _setup.xml. If found it will do it's best to read the list of files and installation folders. It will then convert the installation paths to work from the \Windows directory in both the initflashfiles.txt and RGU files, making it more ROM friendly. You will still have to manually look over the file list and "Additional Registry Entries" generated. It's possible that paths can still be simplified to make it run from a single folder, but it really takes a human to make those kinds of decisions.
Click to expand...
Click to collapse
and
This means your OEM contains a filename which is already used by another OEM you've included in your build. You need to rename that file if possible, and change any references to it in initflashfiles.txt or the RGU file to match the new name.
If the file is _supposed_ to overwrite the one included from another OEM you still need to rename it and use initflashfiles to copy over the original.
Click to expand...
Click to collapse
So...you can keep fighting the software to get it to work the way you think it should, or you can edit a few lines, rename a file or two, and be done with it.
joemanb said:
So why do you need to use OEMizer now that you're doing manual editing, just finish the package. OEMizer doesn't do any special magic that's needed to make your package work in a kitchen.
When your ROM boots is when the files are copied from the windows folder to the paths in intflashfiles.txt. All the files of your ROM originate in the Windows folder after the device boots! In your example, iLock2.lnk is copied from the windows folder to two different locations. THAT file (iLock2.lnk) is probably contained in the cab twice thus you get a dupe error WHEN OEMizer TRIES TO COPY THE SAME FILE TO THE OEM PACKAGE TWICE. When I asked "Doesn't OEMizer put all the files in the same directory for an OEM package?" it was rhetorical.... Watch my lips...
"an OEM package has ALL FILES IN THE SAME FOLDER!!!"
Also, all the files in a cooked ROM are in the same folder, the Windows folder...thus, THERE CAN BE NO DUPE FILENAMES, not only in the OEM package, but also in THE ENTIRE ROM.
OEMizer is a tool TO HELP YOU BUILD AN OEM PACKAGE (most people do it by hand)! Its not perfect and most of the time you have to edit a line or two in the intiflashfiles.txt and/or rename files (most people don't bother removing the 'generated by' remarks, but that doesn't mean the file hasn't been edited) You have to know how an OEM package works. I don't think you do, because you didn't even try my solution, anyone who knows how and OEM package is put together would look at it and say "Ah yes I see". What you need to do is create a few packages manually to increase your understanding of how to put together a package. The software isn't helping in this regard.
When you come asking for help and then reject a workable solution because you're 'so dang smart', well, it just sort of irks me.
Why do I even bother trying to help...
BTW did you bother reading the OEMizer help file...Here are a few entries that indicate that the files need to be manually edited:
and
So...you can keep fighting the software to get it to work the way you think it should, or you can edit a few lines, rename a file or two, and be done with it.
Click to expand...
Click to collapse
It's strange, i was pointing out a problem in the program, trying to better it a little for future users. You, on the other hand, simply chose to attack me for no other reason than trying to act superior. I was hoping someone might know a way "around" the problem (you know, the reason this place is here for) and you didn't know the answer so you chose to show your hide.
There's obviously no way around the duplicated files, such as a sub-directory implementation and that's really what you could have said to begin with. The thing is, the code i had seen had been both hand-coded AND OEMizer was used so i was confused because i thought someone knew a way around the problem. It was something to have easily been confused by. He also renamed the files but must have done some coding to make SU2U recognize the alternate filenames, also something that might have confused the situation.
While i was initially wrong, there were reasons but you chose to ram it down my throat when i simply made a mistake in recognizing Naigman's changes vs using the original files. I've been working at a terminal for close to 12 hours so i'm entitled to miss a few things.
While i'm sure, because you're a senior member, i'll probably be banned. Still, you were just as wrong in the way you handled it as i was and we both know it.
However if you don't know the answer, simply say so.
here is your question from your first post:
Does anyone know how to work around this problem?
Click to expand...
Click to collapse
I gave you the answer, a work around for your problem, you rejected it (without trying it)....You said I was wrong...
that can't be right
Click to expand...
Click to collapse
After you insulted me, I spent my time trying to explain to you how the files all go in the same folder, and that you should build some packages manually to increase your understanding. I said I was irked by your response. I still can't see where I attacked you. I admit my tone was a bit offputting, but I tend to get that way when I'm insulted after making an attempt to help someone who obviously doesn't understand what they are trying to do.
And of course you STILL haven't tried what I told you to do.
Now you say:
There's obviously no way around the duplicated files
Click to expand...
Click to collapse
YES THERE IS.. I told you what to do. I thought you were trying to make an OEM package. The bottom line is making the OEM package work, not whether OEMizer works. OEMizer is a free tool that has documented in the HELP file certain situations where it won't work properly. If you'd have read the HELP file, maybe you wouldn't have had to start a new thread.
I was hoping someone might know a way "around" the problem (you know, the reason this place is here for) and you didn't know the answer so you chose to show your hide.
Click to expand...
Click to collapse
After that statement you still expect people to help you. You insult me again. I hope alot of people see this and see what they can expect from you if they try to help.
I tried to help you by giving you a workable solution SO YOUR OEM PACKAGE WILL WORK. In return I get insults and rejections..My bad I guess.
You just can't help some people. Good luck, You're gonna need it with your attitude.
BTW :
While i'm sure, because you're a senior member, i'll probably be banned.
Click to expand...
Click to collapse
Dude, now you're just cracking me up..
joemanb said:
here is your question from your first post:
I gave you the answer, a work around for your problem, you rejected it (without trying it)....You said I was wrong... After you insulted me, I spent my time trying to explain to you how the files all go in the same folder, and that you should build some packages manually to increase your understanding. I said I was irked by your response. I still can't see where I attacked you. I admit my tone was a bit offputting, but I tend to get that way when I'm insulted after making an attempt to help someone who obviously doesn't understand what they are trying to do.
And of course you STILL haven't tried what I told you to do.
Now you say:
YES THERE IS.. I told you what to do. I thought you were trying to make an OEM package. The bottom line is making the OEM package work, not whether OEMizer works. OEMizer is a free tool that has documented in the HELP file certain situations where it won't work properly. If you'd have read the HELP file, maybe you wouldn't have had to start a new thread.
After that statement you still expect people to help you. You insult me again. I hope alot of people see this and see what they can expect from you if they try to help.
I tried to help you by giving you a workable solution SO YOUR OEM PACKAGE WILL WORK. In return I get insults and rejections..My bad I guess.
You just can't help some people. Good luck, You're gonna need it with your attitude.
BTW :
Dude, now you're just cracking me up..
Click to expand...
Click to collapse
We can continue this, in private. I've got better manner than to turn this into a flame war and that's exactly what you're building it into.
You have absolutely no manners, but a huge ego.
here's your package. it was a piece of cake.
I used OEMizer, but there were dupes and other problems, so as a workaround I had to rename some files and edit initflashfiles.txt just like I said in post no. 3
joemanb said:
You have absolutely no manners, but a huge ego.
here's your package. it was a piece of cake.
I used OEMizer, but there were dupes and other problems, so as a workaround I had to rename some files and edit initflashfiles.txt just like I said in post no. 3
Click to expand...
Click to collapse
Good one, but like i said..figured it out.
Plus, for the record (once again), these people don't know about the private argument we had and it doesn't take a genius to figure out that when someone smears you (in private) and then does something like this (in public) that basically they're trying to smooth over the rep to the general populous. I told you, in the private letter, i figured it out so there was no reason for you to post this other than to make yourself look good to the readers.
For the record, here's just one quote from that novel you sent me, showing how absolutely thickheaded you are:
Basically, i can't prove it yet but i think you're completely wrong about that theory that everything goes into the \Windows directory (first) and then branches out.
Click to expand...
Click to collapse
HA HA HA that's a good one! When you prove it, let me know, in the meanwhile I just wanted everyone to see what they can expect from you if they try to help you. I'm outta here, don't PM me again.
joemanb said:
For the record, here's just one quote from that novel you sent me, showing how absolutely thickheaded you are:
HA HA HA that's a good one! When you prove it, let me know, in the meanwhile I just wanted everyone to see what they can expect from you if they try to help you. I'm outta here, don't PM me again.
Click to expand...
Click to collapse
What you forgot (on purpose it seems) is that i mentioned something about the files hitting the "root" directory then things get built on a first rom install. Man, you're really desperate to get the last word in, even if it means only quoting "part" of what someone says to try and make them look bad.
But since you decided to steal something from our private email i think i'll do the same. You're big on telling people what they should and shouldn't be doing, you even go as far as to tell people where they should be putting their posts because "you" don't think they belong there, i found that one in a 30 second Google. And i'll go as far as to mention that, during our private email, i asked you to list your credentials that makes you so qualified to give the last word on these subjects and you were glad to insult me but never gave an answer.
I think these people already "know" what they expect from YOU, you talk a big game but other than changing a few registry entries around and using someone else's compiler, basically you're no more experienced than the rest of us here...even if you act like it. If you think editing text makes you some end-all be-all expert, man you're seriously deranged.
It seems that "senior member", in your case, is nothing more than a title.
i mentioned something about the files hitting the "root" directory then things get built on a first rom install.
Click to expand...
Click to collapse
Wrong again.
You don't need me to try and make you look bad, you're doing fine on your own.
joemanb said:
Wrong again.
You don't need me to try and make you look bad, you're doing fine on your own.
Click to expand...
Click to collapse
And yet, not once have i been wrong about you. You keep acting like you want this to be over but you just HAVE to get in the last word with things...because that's the kind of jerk you are,
You can call the admin, you can try and make me look bad by trying to play the readers, but anyone with any common sense knows that if you REALLY wanted to stop....you would have stopped replying to my messages.
You've already threatened me, privately..."i'll call the admin if you don't stop PMing me"...yet you're the one that keeps aging it on.
In every way, you make me right...simply because you're that sort of person who just has to get the last jab in. They only way you will make "you" right is to stop posting on this, that's the ONLY thing that will make you look like you're not looking for a fight.
I know it and everyone reading does.
Thanks guys
whewf! After reading through your arguments in 20 posts I finally got what I was looking for. Can you guys please keep it just a little professional and discuss your problems private?
I downloaded the attached file, looked at initflashfiles.txt, examined it and figured out what I need to do for a different cab.
And by the way I personally would be very very happy if someone even considers replying to my posts let alone fixing my problems. But I rather using search tool because 99% of the time someone already asked that question and it has been answered. So please keep it short and easy to understand for everyone.
Thank you,