Stuck in shortcut hell
 

OK I am back again. Can someone tell me why and the hell I can't copy a link to the program folder. I have several OEM's and all are working but two. They were working and just stopped working. My initflashfiles.txt looks like this Directory("\Windows\Start Menu\Programs"):-File("BTAudio Today.lnk","\Windows\BTAudio Today.lnk"). The shortcut works fine and I can manually copy it over but it will not work on flash. I have tried copying working links and init files over and just renaming the info. I have tried creating them all over again. For some reason they just will not work. As always your help is greatly appreciated.

I have the same problem. I have used OEMS in other ROms without issue, but sometimes I get the same thing. I rebuild it at time and they suddenly work again. Not sure why. If you figure it out let us know.

This is driving me crazy. I have rebuilt the oem's atleast 10 times now from scratch each time and I can't get the shortcut to copy :evil: I wish somebody had an answer for this one.

Are you saving it in unicode?

Yeah. The thing is I have even copied the files from other oem's that are working just updating the program info and it won't work. And it worked this morning. I only have two that aren't working btaudiotoday and o2. All of my other ones work fine.

OK after another 10 flashes I have somewhat of an answer but I don't know what is causing it. Maybe somebody else already knows this but since I am new to this maybe somebody else can chime in. It has something to do with the order the folders are in. I took the existing folder BTAudioToday and put an X in front of it. This locked the phone up completely. I then put a V in front of it and it broke my VJCandela 0.3 shortcut. I put a W in front of it and it broke my WM5torage 1.7.3 shortcut. Then I realized that it broke after adding my Bejeweled OEM. So at that point I thought it had something to do with the folder names starting with the same character. But I put a J in front of it since I had no other J folders but it still didn't work. I am not sure what is going on but the work around was to add the entries to a working init file.

Maybe if you take a look at the initflashfiles.dat, it would give you some idea. It's possible it's not either one of the affected OEM's but other ones that aren't completely formatted properly (such as not having a blank line at the end).

Just be cautious when modifying the initflashfiles.dat directly. If you modify and save it, you'll have to hexedit it and remove the first two bytes (FF FE) in most cases. Has to be unicode as well of course.

What? You have to add a line at the end? That wasn't in the how to instructions I read so I had no idea. Damn where were you 25 flashes ago :lol: I hope that does the trick.

isamu49 you are the man/woman. If you were a woman I would kiss you. That was exactly the problem. I went back in to all of my OEM's and added the blank line and now everything is perfect. Thank you so much for the help!