Bug in "Portable Apps in PE!" script/program

The "Refresh ppApps" program in the "Portable Apps in PE!" doesn't appear to recognize a ppApps folder on the B: drive.  I have a script that runs at bootup that copies programs from my lash drive into B:\ppApps at boot time, then runs ppAppsGenPE to generate the shortcuts.  I then changed the ramdisk to W: and changed my script copy, and it is able to create the shortcuts fine from there.

ppApps folder on B drive (ramdisk)?  No go.
ppApps folder on C Drive (hdd)?  Shortcut created OK
ppApps folder on W drive (ramdisk)?  Shortcut created OK

probably,
ppapps ignores checking A: and B: , since they are technically reserved for floppy/tape, to speed up scan route...
It is a general approach on such drive scan utilities....

I do not know the plugin well, but if all this magic made by PortableApps.com utility,
than get in touch with them, and ask to add a routine like:
check A: B: (registry, device manager blabla, not physical but through disk management ;)) --> if NOT floppy --> include at search routine --> and things back to work nicely with B: ;)

If all this magic made by things by amalux, well I don't know, amalux away for a while, I hope he will be back in time...

Chris may have more information about this matter 

The "Refresh ppApps" program in the "Portable Apps in PE!" doesn't appear to recognize a ppApps folder on the B: drive.  I have a script that runs at bootup that copies programs from my lash drive into B:\ppApps at boot time, then runs ppAppsGenPE to generate the shortcuts.  I then changed the ramdisk to W: and changed my script copy, and it is able to create the shortcuts fine from there.

May I ask what script you are using to run your bootup stuff? I just finished a mod to ChrisR AutoRun script to work with Gena. Also I use a program called nircmd.exe. It is a shortcut creator and will create shortcuts from anywhere including your USB drive without coping your stuff to B. Example

Code: [Select]

nircmd shortcut "yourusbdrivehere:\yourprogram.exe" ~$folder.desktop$" "yourprogram"

or

Code: [Select]

nircmd shortcut "yourusbdrivehere:\yourfolder\ifyouneedsubfolders\yourprogram.exe" ~$folder.desktop$" "yourprogram"

I'm using the "Portable apps in PE!" script, it has a program called ppAppsGenPE  in it which does the shortcut creation.  The copying files thing isn't REALLY necessary, but at work I diagnose/repair a lot of PCs, and being forced to keep the flash drive plugged in would be a huge inconvenience.  So, the solution is to copy the programs to the ramdisk.  This way, I get the benefit of being able to customize the programs in the PE environment without rebuilding AND I'm able to unplug my flash drive and move to the next PC.

If you're curious how I do it, the (cmd file) script is like this, and it's stored in the system32 folder and told to run at boot:

Code: [Select]

for %%a in (c d e f g h i j k l m n o p q r s t u v w y z) do (
DIR %%a:\ >NUL 2>&1&&if exist=%%a:\AwesomeApps (set configdrive=%%a:)
if exist "%configdrive%:\Config\Copy AwesomeApps into RAM.yes" (
xcopy "%configdrive:\AwesomeApps" "W:\ppApps" /e /i /h /r /y
ppAppsGenPE.exe
exit
) else (
exit
)

While I have my flash drive set to become Y: automatically when booted, I've noticed sometimes it doesn't due to the computer having a failing HDD or something and taking longer to detect, so this script searches all the drives that the flash drive could be then copies from that one.

ppAppsGenPE is amalux's utility,
I also guess you use amalux's portable package at AwesomeApps ;)

and ppAppsGenPE do not search-find  B: drive, since amalux not around ..... (I hope he is okey) ...

Until amalux around and fix / adds ppAppsGenPE (be sure I will get him notice when he is around),

the only quick solution seems to be assigning another driver letter for ramdrive like you do with W:



about your usb assign troubles,
similar problem also here
http://theoven.org/index.php?topic=354
and reported numerous times, so far a delay made to wait Windows get ufd ready......
it seems to be and hardware trouble
 (well, testing such "trouble" usb-boot hardware with Win7PESE and Gena sidebyside would clear if it is OS or Hardware trouble ;))

so far only solution at hand, seems to me, using (testing) FAT32 and see if it helps....