PI 12 w/update pack in vista, crashes trying to load gallery

[immersive]

I'm trying to get my custom Easy Palette gallery into PI 12 on vista ultimate 64bit final. I have already installed the update patch that supposedly supports vista. After I right click and select "Load" in the Easy Palette, the file browser comes up to select a file to load, then if I select a folder or file the programs crashes instantly. I need to be able to use my custom presets while designing. Does anyone have any ideas on how to fix this issue?

Problem signature:
Problem Event Name: APPCRASH
Application Name: Iedit_.exe
Application Version: 12.0.0.0
Application Timestamp: 45a48671
Fault Module Name: Iedit_.exe
Fault Module Version: 12.0.0.0
Fault Module Timestamp: 45a48671
Exception Code: c0000005
Exception Offset: 000b890c
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 8d13
Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
Additional Information 3: 8d13
Additional Information 4: cdca9b1d21d12b77d84f02df48e34311

[Aaron]

I just tried to load my presets into the gallery and had the same problem. Instant shut down of pi12. No error msg. or anything it just shuts down. There is also a problem with the screen capture feature. The select area mode does not in fact allow you to select anything which cause you to stuck in the screen capture and the only way to get out is ctrl-alt-del and shutdown. I have contacted pi tech but they sent me directions for win XP and it was just the generic delete pi12 and reload it. Anyone have any ideas.

[skyml]

Having the exact same problem.... can't load my custom gallery from PI11 into PI12 on my Vista machine. Also noticed there is no preview of UFO files in Explorer under vista. Come on Ulead - fix these issues.

[immersive]

Yes, this is really annoying. You would have thought that these issues would be fixed with the so called vista update patch right? Nope.

[renardin]

I found the solution, do not click the icons, just type the name and you will be ok.



now where is the vista patch as I saved you all?

EDIT: I found it.

[skyml]

Tried that and it worked after about 3 tries.... 2 emails to Ulead about this error and no reply so thanks for the tip! Now I just wish that the thumbnails for my UFO files would show in Windows Explorer under vista - feel like I'm using an older version of PI.

[renardin]

Can a moderator make this topic as a "sticky"?

It's still the only way for importing a gallery. I forgot to mention, make sure the file is in the "Documents" folder.

[sjj1805]

Thank you for sharing this with us. Moved to the Vista thread.

[Drakonix]

SUBJECT: PhotoImpact 12.0.0.0 crashes after loading in Windows Vista Ultimate (Vista update patch applied).

Nature of the problem: Installation steps taken

PhotoImpact 12 (Upgrade) installed from CD, new key and old (upgrade from PhotoImpact 11) key entered
Custom install, electing to only install PhotoImpact 12 (also tried with complete install, with same result)
PhotoImpact 12 patch applied (For Vista) from download
Launch PhotoImpact 12
PhotoImpact 12 workspace screen appears full screen
"Welcome to PhotoImpact" window appears inset on workspace screen

When mouse cursor moves onto "Welcome" screen, desktop becomes whitewashed. Clicking on anything causes error message "PhotoImpact has stopped working" and forces you to close the program.

A couple of uninstall/reinstall cycles attempted with same result. Running install and/or application specifically as Administrator (¡§Run as Administrator¡¨) does not help.

Computer HD 1.5 TB RAID array has two partitions of approximately equal size. One partition has Windows Vista Ultimate installed on it and the other partition has Windows XP Pro SP2 installed on it. This allows me to boot Vista or XP using the same exact hardware.

Upon booting XP Pro SP2, and performing same installation steps as above, PhotoImpact installs and runs normally.

I consulted the Knowledge Base (¡§VISTA compatibility for old versions¡¨) and found reference to the Windows Vista Program Compatibility Wizard. The Knowledge Base does not tell you that in order to see the link to the Program Compatibility Wizard the Control Panel view MUST be set to ¡§Category¡¨. If you have the Control Panel view set to ¡§Classic¡¨ (as I did) you will not see the ¡§Use an older program with this version of Windows¡¨ link to the Wizard. I found this critical information with a Google search on ¡§Windows Vista Program Compatibility Wizard¡¨.

Using the Program Compatibility Wizard to force compatibility to Windows XP resolves the issue. Compatibility mode was used to install and subsequently run PhotoImpact 12.

Therefore, it seems the patch to PhotoImpact 12 to address Windows Vista compatibility is not entirely effective.

Properties of your source files: None Loaded

What devices are involved and their mode of connection? Does not apply

Project Settings: Default from new installation

Output format (file, DVD, VCD, SVCD): Does not apply

PAL or NTSC: NTSC

Error Codes (if any) :
"PhotoImpact has stopped working"

Problem Event Name: APPCRASH
Application Name: Iedit_.exe
Application Version: 12.0.0.0
Application Timestamp: 45a48671
Fault Module Name: uliblzw.dll
Fault Module Version: 12.0.0.0
Fault Module Timestamp: 44e0a2e5
Exception Code: c0000005
Exception Offset: 00002b86
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 1e54
Additional Information 2: aa05aaeb3dbfc6d9180d62a22a4fb53c
Additional Information 3: 4858
Additional Information 4: d5edb16bc82b4280b302dc916c0ba5ed

[sjj1805]

Hmmm interesting - Because I only recently bought a laptop with Vista pre-installed I overlooked the 'Vista update patch' and just installed PhotoImpact 12 on the laptop and (so far) have had no issues with it.

Perhaps you could try doing a Clean re-installation and NOT install the update pack to see what happens.

[Drakonix]

It wasn't clear in my original post, but I tried an install from CD (without the patch) first. When the installation would not work, I went to the Ulead website looking for a possible Vista related update and downloaded the patch.

Then, I tried a clean install (meaning uninstall PI12 using Control Panel and re-install) from CD and applied the patch before attempting to launch PI12. I overlooked the special, advanced uninstallation instructions. That could have been a factor.

The PI12 CD I have is an upgrade installation (from PI11) and I installed it to a HD on which PI was not previously installed - this might have significance in the matter. When the installer doesn't see an upgrade qualified installation present the installer just asks for the upgrade qualified serial number, to which I supplied the serial number of my PI11. However, installing PI12 under the same circumstances in Windows XP Pro SP2 does not produce the problem that occurs with Windows Vista Ultimate. PI12 operates normally on Windows XP Pro SP2 with or without the patch.

[Drakonix]

I have resolved this issue and post it here for the benefit of others.

The issue I experienced is confirmed to be a hardware issue specific to the Xerox Documate 510 scanner and the Windows Vista compatible driver available for download on the Xerox web site. I have had the scanner for slightly less than one year.

There are two hardware versions of the Documate 510. The newer version is an RoHS (Reduction of Hazardous Substances) program version. The RoHS version uses completely different parts from the earlier, non-RoHS version.

The newer Windows Vista compatible driver does not support the "legacy" (earlier non-RoHS) scanner hardware. If you have the older version of the Documate 510 scanner, it can not be used on Windows Vista unless Xerox updates the driver in the future to support the legacy hardware - which is unlikely.

The only way to tell the new version from the old version is to examine the label located on the bottom of the scanner. There will be a number beginning with 85 with the following format "85-aaaa-bbb" where aaaa and bbb are numbers. If the bbb value is "000" the scanner is the older version (and NOT Vista compatible). If the bbb value is "100", it is the newer RoHS version which is supported by the Windows Vista compatible driver.

You wouldn't believe the tap dance I got from Xerox Support. It took three tries over two days to get the real answer out of them.

During the first support call this electronics engineer was told that the scanner would only work properly if plugged into a USB port on the rear panel of the computer, and would not work properly if plugged into a USB port on the front of the computer. The explanation was that the two additional connectors and approximately 12 inches of cable introduced excessive signal loss which would prevent the scanner from working properly. The instructions were to uninstall the driver, plug the scanner into the back of the computer and re-install the driver.

Unfortunately, the scanner USB cable would not quite reach the back of the computer. Knowing what I was told was inaccurate, I still re-arranged the office area somewhat so I could plug the scanner into the back of the computer as directed.

It was not surprising that the scanner would still not work after following the instructions. This necessitated a second call to Xerox support.

During the second call, I told the support tech that I had two physical hard disks in the computer and could boot either Windows Vista or Windows XP Pro SP2 on the same system. The scanner would work properly in XP but not Vista. I was then told that this constituted an "advanced installation" and was ineligible for support. The tech insisted that the Windows XP hard disk must be physically disconnected while booting Windows Vista from the other hard drive.

Knowing that this was also inaccurate information, and not knowing what excuse Xerox would come up with next, I decided to move the experimentation to a test bed system I have for testing hardware and software. Over the span of most of a whole day, I partitioned and formatted two hard disks and installed Windows XP Pro SP2 on one of them and Windows Vista Ultimate on the second drive. I did Windows Updates so that both OS installations had all the current updates. Then, I repeated the tests I had tried on the first system, using only one drive connected at a time in accordance with what Xerox support told me. The failure was easily reproduced. This prompted a third call to Xerox support, where I was finally told the truth (that the Windows Vista compatible driver does not support the legacy hardware version of the Documate 510).

You can not determine the scanner version from markings on the outside of the box, you have to take the scanner out of the box and look at the above mentioned number located on a label which is on the bottom of the scanner.