nobeefstu

Jim M, If Anthony's method above works easily for you ... use it. There is a provison in PTE to add your own image editor ... however its not a easy user task performed from within the menu functions of PTE GUI. Im not sure if this old function is even documented in PTE Help anymore ... but the function is still possible. Look for the programs installed User directory ... find the Apr.ini file. On Xp its located in All Users or the current named users directory depending on how it was orig installed: C:\Documents and Settings\All Users\Application Data\PicturesToExe\Versions\6.0\apr.ini Once you find the Apr.ini file ... open it with Notepad and search inside the documemt for the text string: GfxEditorPath= Enter the full file path to your own preferred image editor after the = sign and save the document. Example: GfxEditorPath=E:\Image_Xp\PhotoFiltre Studio X\pfstudiox.exe Your CTRL+W key function should now work and open your image editor from within PTE.

Peter, Actually, Ive never read much or studied enough about 64bit to offer any new insight or information on the subject. Im somewhat like you in the respect where converting to 64bit does little to benefit my current needs and uses. I dont do high volume image editing or video processing on a regular basis to warrant the change anytime soon. I usually upgrade system, hardware, and software as my needs require ... 64bit processing may benefit some users current needs but its not a top priority for me.

jdearman, Thanks for the updated info. I had thought since you were in VideoBuilder and trying to burn in Blue-Ray fornat you had overcome your issue burning in the normal DVD-format. I suspect since you have a new PC with a brand new multi-format burner ... the current version of VB DVD burning library files have no instructions to specifically identify and configure your new burner. When there is no specific instructions available the burning process usually resorts to default settings in a hopeful attempt to burn a disc. However, this is like shooting in the dark and one never knows exactly what the end result will be. Igor subscribes his DVD burning library and once they update their library files to him ... they are usually included in his next version releases. Your Key issue appears to be a different and somewhat isolated issue related to just a select few PTE users.

Hopefully some other users of CS4 and PTE 6.0 will come to offer their solution. Seems CS4 is trapping the <ESC> key and locking out others use. 1- Do you not have the <ESC> key issue when using the Preview button ? 2- Does this only happen when in Objects and Animation panel view or also when in the Slide panel view ? Try these tests if they work around your issue: 1- Use <F5>+<ESC> key combination to escape from the current slide preview. 2- Minimize CS4 first then use PTE as normal. Minimizing CS4 may hopefully release its trapping of the <ESC> Also Note: Try PTE Version 6.0.2 released (January 19, 2010) if you havent already.

jdearman, My post is not related to your current Blue Ray burning question. I recall you having issues with PTE-VB amd your new Windows 7 as posted in the topic - For those who have problems with Windows 7 and PTE In an effort to keep other Windows 7 users updated ... Have your issues with PTE-VB and Windows 7 been completely resolved now ? If so, please make a comment to update the topic - For those who have problems with Windows 7 and PTE with whatever actions resolved your issues to help other users. Thankyou.

Gnim, If your posted sizes are in kb ... that makes your DVD Disc about 2.19 GB Are your DVD Discs 12cm (diameter) DVD-5 (4.7 GB) type or something else ? VideoBuilder will also burn your ISO file ... open VB GUI and from the top bar menu select File|Burn ISO Image. Many users are anxious to burn at the fastest speed possible which can sometimes promote burn issues. Do yourself a favor and move the setting down a few notches to a medium burn speed to obtain less chances of issues. But as Peter has basically said ... you cannot put more data on a disc than the disc allows. Also allow some space is lost to disc formatting so your not going to get 4.7 GB of data on a 4.7 GB DVD.

Just posting some of my notes to help users understand the use of dot{s} . or .. in the filestring. Example filestring with 2 dots as documented in some .pte files: E:\1_Mmb\..\Media\4_Music\3Waves\smooth.wav Two dots ("..") are used for moving up in the hierarchy, to indicate the parent directory; one dot (".") represents the directory itself. Both can be components of a complex relative path (e.g., "../mark/./bobapples"), where "." alone or as the first component of such a relative path represents the working directory. (Using "./foo" to refer to a file "foo" in the current working directory can sometimes be useful to distinguish it from a resource "foo" to be found in a default directory or by other means; for example, to view a specific version of a man page instead of the one installed in the system.) MS-DOS/Microsoft Windows style Contrary to popular belief, the Windows system API accepts slash, and thus all the above Unix examples should work. But many applications on Windows interpret a slash for other purposes or treat it as an invalid character, and thus require you to enter backslash. One of the prime examples is the cmd.exe shell (often called the "terminal" as it is typically run in a terminal window). Note that many other shells available for Windows, such as tcsh and Windows PowerShell, allow the forward slash. In addition "\" does not indicate a single root, but instead the root of the "current disk". Indicating a file on a disk other than the current one requires prefixing a drive letter and colon. This is not ambiguous because colon is not a valid character in an MS-DOS filename, and thus one cannot have a file called "A:" in the current directory.

Seems like everyone here has things under control ... ? I do know that WMP likes to reopen using its last previous state. I still use WMP v9 and there is no way to completely exit directly from Full Screen ... without closing Full Screen first. I dont know what View settings you are using in WMP, but if you play with the View|Video settings and disable checkbox Fit Player to Video on Start you may be able to overcome your described issue as I understand it. But with all these different WMP versions and updates ... who knows

I agree with Kens comment On one of my Drives that I have excluded Norton to check ... everything is normal and fast with the new icon. On Drives with Norton it slows down somewhat to fully appear. I also suspect since the new icon file is 55.5kb and contains alot more icon resources ... its taking longer for Norton to check it. The old icon file is only 3.55kb and contains very little icon resources. Peter, As to your Ive noticed somewhat the same delay behaviour (maybe 10-15 sec tops on my Xp) ... and I found this behaviour directly related right after Norton does its update. After that all is back to normal with no delay till the next update. I dont use the Pulse update setting but this may be more noticeable for users that do use it. ** It just shows how much more influence all these various Protection programs today are impacting the behaviour of our PC from what we use to experience.

Eric, See the attached image for the button object filestring location. Copy the entire text content as displayed in your button setting and paste it into your Forum post. Taking a screenshot may not reveal the entire text content. At least we will see what your trying to run and have to sort it out from there.

Eric, As far as Im concerned ... it you dont want to supply just your Menu.pte file (no images, sounds files etc are needed) thats upto you. All thats required for me to review your issue is that you just supply the filestrings you exactly entered into your button objects to launch the problem slideshows. Revealing the filestrings you used will not compromise any user(s) material. You will do yourself a great service to enable the "show all files" ... now at this stage with your current experience and knowledge with a PC. It becomes quite a handicap to anyone who builds any type of program not to be able see what files and extentions they may need to work with. Its hard to understand the workings of a PC if you cannot see whats on it.

Eric, Jim is quite correct ... the picture does not show us the filestrings used to launch the problematic slideshows. It would benefit you to check the File Properties of the problematic slideshows and see what program your PC has (or has not) registered for the default opening of the file. Also after you right-click the File the bold text displayed atop the selection list panel denotes the default file action used when the file is double-clicked. Your PC configuration on registered File Types may need some changes/additions to properly open the file the way you want and the program you want to open it. To totally avoid any such changes or additions to your current File Types configuration ... you need to specifically call the required program to open the file in your PTE filestring. First, you need to determine what specific program is required to best run the file. Please note ; To call or open with a specific program ... that program must be installed on your PC. Also remember that all programs cannot open just any file extention and not all programs accept calls to perform parameters or command functions. It can get both complicated and confusing at times ... and sometimes it just cannot be done. Hopefully your issue is simple to resolve

misterk, Have you verified you have installed (or properly installed) the NVIDIA video card driver required for your Windows7 ? By your comments it almost seems your Windows7 OS may still be running the original windows generic display driver. As to your Menu page slideshow not working correctly on Windows7 ... first check if your path strings within the PTE file are Full or Relative filepath strings. Relative filepath strings are best/required when using or copying to other PC users or OS.

Johann van der Walt, First lets address your comment below : There is no need to call Acroread32 if you dont care whether or not the user has Acrobat reader installed. Actually you may be limiting yourself whereas your users only with Acroread32 can open your PDF documents. If you use just the relative file string "supportingdocs\detail1.pdf" ... this should be sufficient to open in any PDF Reader a user has installed on their PC. If the user does not have a PDF Reader then the file wont open anyway. The only need I see to use Acroread32 is if your installing the PDF Reader (portable type) on the CD Disk. But, then you must use its own path string and not the systems. The commands/strings you want to use if your still determined to do things your own way is : Relative folder designation: Acroread32 "supportingdocs\detail1.pdf" If your working from the Root of a Drive you can also use/lead your filestring with \

Dan, My first take on your issue was a Direct X issue. But you did say 'I did : update all my drivers' ... did that also include re-installing the DirectX 9c version drivers as well ? Can you be little more descriptive here with almost and what it actually involves. Do all your compiled PTE exe slideshows (new & old) play as expected or do they also have the same issue ? You never did say what model Video Card you are using ? Adding big pan&scan functions may be beyond the limits of your model Video Card capabilities. Plus also run a complete Direcr X Diagnostic test to assure all is up to par in that department.. As Peter says 'Trying to diagnose this kind of problem when we cannot see what you see is a real challenge' ... then add to it possible spyware/malware removals and what ever registry changes/cleaning that may have resulted.

Another good thing to do once in awhile or just after setting up your new PC is to check all your various ports and services that may be wide-open and vulnerable on the internet. I often check with Steve Gibsons ShieldsUP site to probe my PC ports for any changes they may result after time or from some update or whatever. If your running completely Stealth your doing AOK. ShieldsUp https://www.grc.com/x/ne.dll?bh0bkyd2

Keith, Most likely you forgot to include some file content or order of the file content. However, most users find its easiest just to use the Create in Zip feature rather than the Create to avoid missing some of the content when copying the files for Mac users.

Anthony, I have not found a way for the user to change the New default icon within PTE GUI or its ini settings files ... nor does the Registry offer a bypass method. The only recourse I see is that you must personally load the PteViewer_Old.ico located in the PTE program folder using the Assign Icon for Exe File provision within the Project Options. Note: You could make a blank v6 Template with the PteViewer_Old.ico already assigned ... so as not to have to load and assign the icon for each new project. Use the Manage Templates provision and enable the checbox for Default Template for New Projects.

DaveOR, At least now we can confirm something has been written to the Registry in the way of a VB Key. The only way to resolve this issue with your Key is to contact Wnsoft Support ... http://www.wnsoft.com/support.htm If you still have your other or another PC (XP or Vista) to test if this VB Key works on another OS ... at least you know its just a PTE/Windows 7 problem and not a problem with the actual VB Key. It would also be helpful to verify whats actually written in the Windows Registry exactly matches whats written in the VB Key txt file ( all the string of characters in the Key=value) The more you know ... the more you can report to Wnsoft. Note: The Signature area lies at the bottom of every Post. Some users dont use it ... but here is what mine looks like. KeyCopy cannot help with your issue ... its still a useful tool for all users when the need arises. Click the KeyCopy.

denwell, My tests dont show a problem here. I believe it to likely be an illusion and may well be more apparent depending what other colors are in the image or background. It could be also your monitor refresh or response rate time is helping to influence the burn-in visual changes. My monitor rate is 2MS. Have you tested on other monitors to check the effect ? Is it more apparent in slow or fast fades ?

DaveOR, I dont advise people to edit the Registry directly unless they feel absolutely certain they know what they are doing. The Registry has no confirmations or messages to save on exit ... it just automatically enters whay you type in after you click OK. From the Start Menu - Run command just type in regedit I have provided 2 attachments of what things should exactly look like on a XP OS. The 1st top listing (Default)(value not set) is pretty much normal for any and all registry entries. See my Signature below for KeyCopy link details. KeyCopy will atleast tell you if a VB key currently exists in your registry. However, it cannot tell you if its a valid key value or entry. Sample Key.txt

RalphA, Basically your older expired Dec 20th VB Key will always work as normal for anything you build using the PTEv6.01 released Dec. 3, 2009. Any future PTE versions released after your expired Dec 20th VB Key will require your new VB Key. See this post from Igor : http://www.picturestoexe.com/forums/index.php?showtopic=10089&view=findpost&p=65868 Since your older expired Dec 20th VB Key is still valid for PTEv6.01 ... PTE is not asking for your new VB Key just purchased. Im not aware of any menu/provisions in the PTE GUI to manually add a Key. The only way I see is for your to hang on till the next future release asks you for your new updated VB Key ... or you can manually edit/add it into the Registry yourself if you feel capable enough to do so.

Andrew, Depending on how your objects are layered ontop of one another ... this is normal behaviour for multiple objects. What you need to use is the Tools button and enable the Ignore Objects Not Selected In particular needs you may need to toggle this operation. I find it quickest just to use the Keyboard HotKey <ALT>+<I> to perform the toggle function as needed.

Peter, My XP Sp2 tests indicate pretty much the same issues as your Vista. The PTE601MenuB.exe-v449 button always launches the S449.exe ... however its not always consistantly ontop and sometimes runs under the PTE601MenuB screen display. When I change the PTE601MenuB.pte file setting to Windowed Mode ... it always runs S449.exe ontop as it should. Using the Fullscreen Mode somehow seems to create the issue were having. Tested same conditions with a PTE v6.0 build and it too exhibited the same issues as the PTE v6.01. build.

Laszlo, Glade you got it sorted out. Reading the PlayView Guide.chm a bit closer helps The Guide already explains the purpose of the red TextBox note : If at the end of the search process PlayView found any exe files that did not pass the search safeguard restrictions a clickable red TextBox will immediately appear. Clicking the red TextBox brings up a savable notepad list of restricted exe files. You may need to check the list for possible Slide Show file names used that were rejected. You may need rename or move any of your PTE Slide Shows so they will pass the search safeguard restrictions. If you don't receive this red TextBox display it means the search did not find any restricted files to notify you about. See Search Restrictions The safeguards were implemented to help the average pc user from miss-using the purpose of the menu tool and to avoid becoming overwhelmed with 100's of unnecessary exe files that may be too sensitive to open if the user is unaware or click happy. Pc users who have a better understanding of their pc and its file content use more caution and know better ... but they too get limited by the search restrictions.