No more WinPE

[John Doe Genius]

Originally Posted by wptski

If it's my user name, it's good enough for Windows so it should be good enough for Paragon...

Not necessarily. We, the old guys, know that filtering rules for valid file names have changed during the course of time. Remember the 8.3 notation, spaces disallowed. I myself, did a mistake “100 years ago”, I created an app using the first 6 characters if the file name as an identifier. Some characters, allowed by MS as a file name, could not be used as an identifier in my application. My native language has characters outside the A-Z sequence. We have learned never to user the national characters in password applications. You never know whether they are fully accepted. The apostrophe is indeed s special character, the OS might handle it, but that is not granted by every application. As far as I can recall, another user had problems with the apostrophe in an internationally well known application (I do not remember which).

OK, I have run BMB with the “Bootable media file” option. Worked smoothly. Two folders were created in %temp%, 'VistaPE' and 'svf15.tmp'. 'VistaPE' was deleted after the completion, but not 'svf15.tmp'. The folder kept 3 .tmp files, give them .png extension, and you will find they are the images from SIW2's post #59 in 'WinPE 3 and USB 3.0'. Interesting!

SIW2's post is a great explanation about how you can integrate your own utilities with the Paragon menu system. I was very proud of my own results after being taught by SIW2, have a look, please: http://www.wilderssecurity.com/showp...8&postcount=61

[wptski]

Originally Posted by John Doe Genius

Not necessarily. We, the old guys, know that filtering rules for valid file names have changed during the course of time. Remember the 8.3 notation, spaces disallowed. I myself, did a mistake “100 years ago”, I created an app using the first 6 characters if the file name as an identifier. Some characters, allowed by MS as a file name, could not be used as an identifier in my application. My native language has characters outside the A-Z sequence. We have learned never to user the national characters in password applications. You never know whether they are fully accepted. The apostrophe is indeed s special character, the OS might handle it, but that is not granted by every application. As far as I can recall, another user had problems with the apostrophe in an internationally well known application (I do not remember which).

OK, I have run BMB with the “Bootable media file” option. Worked smoothly. Two folders were created in %temp%, 'VistaPE' and 'svf15.tmp'. 'VistaPE' was deleted after the completion, but not 'svf15.tmp'. The folder kept 3 .tmp files, give them .png extension, and you will find they are the images from SIW2's post #59 in 'WinPE 3 and USB 3.0'. Interesting!

SIW2's post is a great explanation about how you can integrate your own utilities with the Paragon menu system. I was very proud of my own results after being taught by SIW2, have a look, please: http://www.wilderssecurity.com/showp...8&postcount=61

I don't have a "svf15.tmp" and no ".png" either but if that's after the ISO try, mine failed as mentioned.

If you search you could find posts between me and SIW2 about a year ago or so. Yes, I've fooled with WinPE myself but since I purchased the HDM12S that came with the ability to create a WinPE disc, I lost interest.

I'm unsure how that would go changing my user name on a 19 month old system? If that would require me to reformat and start from scratch, forget that! Reformatting is the last resort which I avoid like the plague.

It's not like Paragon is the only application using my "temp" folder either and others are happy with it.

Don't know if it would make any difference, probably not but you are W7 64-bit but are you SP1 and is your WAIK updated?

[comtrjl]

I wouldn't change your user name unless it were the only solution - I recently had to completely reinstall a machine where the user had changed his name and then tried to fix the 100s of registry entries containing the old name.
Changing the location of the temp folder - and avoiding thereby the use of your user name - is relatively easy; you need admin access. Create e.g. c:\temp, then go to System control panel and Advanced system settings. Select Environment variables at the bottom. There are 2 entries in the top half and 2 in the bottom half referring to TEMP and TMP (one pair for the user, one for the system) - edit each one and change it to c:\temp. Reboot for good measure.
See if that helps BMB.

[wptski]

Originally Posted by comtrjl

I wouldn't change your user name unless it were the only solution - I recently had to completely reinstall a machine where the user had changed his name and then tried to fix the 100s of registry entries containing the old name.
Changing the location of the temp folder - and avoiding thereby the use of your user name - is relatively easy; you need admin access. Create e.g. c:\temp, then go to System control panel and Advanced system settings. Select Environment variables at the bottom. There are 2 entries in the top half and 2 in the bottom half referring to TEMP and TMP (one pair for the user, one for the system) - edit each one and change it to c:\temp. Reboot for good measure.
See if that helps BMB.

Even easier to Run %temp%, select all and delete just for BMB use.

[John Doe Genius]

The suggestion to change your user name, was meant to be a joke. (Like my “strong” name these days, “The Boss”. You know, my wife borrows my computer from time to time. Then she has to log in to my account...)

comtrjl has already told the truth, to change the user name, is a night-mare. I would prefer to create a new account, or modify the environment variables like comtrjl says. And you could use the Windows\Temp folder that already exists.

From post #129 I understand that your problems are solved by emptying %temp%. If that suit your needs, everything is OK.

BTW, yes, I am running Windows PE 3.1 Windows found at http://technet.microsoft.com/en-us/l...=ws.10%29.aspx. The folder 'svf15.tmp' is automaticly deleted if it was empty before BMB is started. My SIW2 files must have been created by another program.

[Erik_FL]

Paragon makes extensive changes to INI and executable files in the boot disc version. If you use the normally installed program folder to create a boot disc it will not function properly. You have to use the Boot Media Builder to create a fully working boot disc.

If you want to make a boot disc using PE Builder or WinBuilder, the information below may be helpful.

I have been building my own Windows XP rescue CD with PE Builder since HDM version 9 and have found solutions for some of the problems. The two most significant problems are that the CD is automatically ejected, and the help doesn't work in the program.

The CD eject problem causes the program to hang if you try to start it from a booted CD (without running the OS completely from RAM).

The help problem causes the program to display a Java script instead of the help.

Both problems can be solved by deleting the "hklm\system\currentcontrolset\control\minint" registry key. To get the Express Launcher help to work one also has to edit "ExpLauncher.ini".

I can't verify this, but it appears that the Paragon boot disc has some mechanism to delete the "MiniNt" registry key while it is running. That means if you try to use the software with a standard Windows PE build it will find that registry key and not work properly. If you are having problems with your own custom build you may want to try deleting that registry key to see if it solves the problems.

You can also supply an extra parameter when running "launcher.exe". The extra parameter is "Dont_Eject". You can modify shortcuts and the "ExpLauncher.ini" to use the "Dont_Eject" parameter.

I have not yet found any solution to the help display problems except deleting the "MiniNt" registry key.

Building with WinBuilder has the same sort of problems for the same reasons. The "MiniNT" registry key is normally defined in a Windows PE system, and the set of files required to run the Paragon Software on Windows PE is undocumented.

[Adric]

Erik_FL

I believe you suggestions only applies to an XP preinstall environment and not Win7 which is what most PE recovery media is based on now-days.

Edit: I stand corrected. The key also exists on my Win7PE. I missed it when scanning.

Al