GOODBYE - off to......................

wymjym · Post by **wymjym** » Sat May 20, 2006 1:34 pm

Hi,
I just renamed the cfg files within ulead 10. tried to restart...here is my little error message:

Error sigmature
AppName: iedit.exe AppVer: 10.0.0.0 ModName: mfc42.dll
ModVer: 6.2.4131.0 Offset: 0008f549

(thanks for the thoughts and effort)
wj

Devil · Post by **Devil** » Sat May 20, 2006 1:52 pm

This shows the stupidity of shared/common files. I have 11 different instances of MFC42.DLL installed on this machine, of 4 different sizes. They are all Microsoft but are used for different proggies. I suggest that it is totally ridiculous to have versions in ...\system32 and elsewhere, even in c:\windows\... (other than in system32). Some MS (and other) proggies have it also in their specific directories. Including C:\windows\..., 3 versions and 8 instances are used for MS applications.

I maintain that the only correct way of programming (and, yes, I have been a professional programmer) is a) NEVER, EVER, have common files relative to a family of non MS applications (e.g., each app must be self-contained and never sharing a dll between apps) and b) where poss, copy MS common files into each app directory and use that one, not the one in Windows\...

sjj1805 · Post by **sjj1805** » Sat May 20, 2006 1:53 pm

You have now revealed something not previously mentioned.
You are using Drive H rather than drive C as your operating system drive.

Although theoretically this should cause no problems this is where theory and practicality divorce themselves from one another.

I have seen several posts throughout this forum where users have chosen to install Windows elsewhere than the default C drive. Similarly problems have been experienced by users installing programs to drives other than the default C drive.

I have several hard drives and use drive carriers so that I can turn off my computer swap a hard drive over in seconds and turn back on again. As a result I have been able to make all sorts of experiments over the years
various methods of multi-boot systems. Mix and match operating systems
Windows 3.11 / 95 / 98 / 98SE / ME / NT4 / 2K / XP / Mandrake Linux.

I have experimented with the method you have used - installing to a drive other than the C drive.

To cut a long story short - if you install to anywhere other than the C drive you risk problems which would appear on face value to be a very good chance of your current isue.

You may be interested in my current 3 Hard Drive set up
http://phpbb.ulead.com.tw/EN/viewtopic. ... 7194#57194
and also in this (not yet completed) Tutorial
http://phpbb.ulead.com.tw/EN/viewtopic.php?t=13421

Sorry to be the bearer of bad news.

wymjym · Post by **wymjym** » Sat May 20, 2006 3:20 pm

I only am using ide drives for removable storage.
I have two perminant sata drives, XP will only assign C to ide type...maybe I can add c to the H look up table?
wj

wymjym · Post by **wymjym** » Sat May 20, 2006 8:25 pm

Steve,
another random thought or two
until I put this current system together I was using PI-10 (and at times 11) on my work system...this one was multiboot with; win98se,win2kpro,winxp-sp2.PI-10 worked fine in each OS and the drives were; C for win98se, E for win2kpro-sp4, F for winxp-sp2.

further, this system that I'm having issues with (just ulead issues) with H as the boot/main drive did initially have UL PI-11 on it and working, I only used it for an hour or so and then never tried again until I had loaded many, many more programs...at which point it refused to start up (same mfc42.dll)
just hoping that more info will help find the fix
wj

heinz-oz · Post by **heinz-oz** » Sat May 20, 2006 9:40 pm

What Steve is saying does make some sense, however, in a multiboot set up, you cannot have all your set ups boot into C, can you?

I have also be warned by many an expert not to have the boot drive in a caddie. Any thoughts on that?

sjj1805 · Post by **sjj1805** » Sat May 20, 2006 9:51 pm

It all depends upon how you set up your multi-boot system.
The Hard Drive Caddies I use enable me to slip the master boot drive "C" out of the computer and pop in an alternative master boot drive.
Think of it as you would an extension lead. Instead of the ide cable plugging directly into the hard drive it plugs into the caddy, then the hard drive plugs into that. Do not confuse a caddy with an external hard drive such as a USB or Firewire Drive.

Its the same as taking off the lid.

The other method of Multi-boot that I use is controlled by the system BIOS.
I have written an article here:
http://phpbb.ulead.com.tw/EN/viewtopic. ... 7194#57194
about how to go about setting up a multi-boot system involving use of the system BIOS.

The method I describe enables you to use one of the other hard drives as the master boot drive and is given drive letter C. The method I describe is also independant of any other hard drives which can in fact be removed from the computer.

The method of multi-boot that most people appear to use is simply having two (or more) hard drives or partitions and simply installing operting systems onto the other drives without changing the boot sequence in the BIOS. This creates a boot up menu and the user selects which operating system to start and invariably the operating system is then assigned a different drive letter, often D.

keenart · Post by **keenart** » Sun May 21, 2006 12:13 am

I have the duel boot configuration, ME on C:\ with XL and WINXP SP2 on drive D:\ with PI10. No mfc problems and do have two versions on the drive and one is the current version HT indicates.

I do know that Nero 6 drag and drop feature can cause problems and had to uninstall Nero and go to Plextor Pro. Don't now if this has anything to do with mfc42.

Sorry not much help. When in this situation I just format and reinstall it all over again and get rid of the problems altogether.

wymjym · Post by **wymjym** » Sun May 21, 2006 12:44 am

'When in this situation I just format and reinstall it all over again and get rid of the problems altogether.'

I know that if you had spent as much time as I have and had installed UL and had confirmed that it worked (at one point in time) and then installed everything else...you would probably rethink that statement.

Steve,
I understand your bios vs boot.ini suggestions. I also have what we call over here
'mobile' racks. I have many hdd that are used for back up and off location storage....they slide into a slot, I copy things over and then remove the entire drawer that has the hdd within it and store it somewhere or another.

This system is xp-pro sp2 and I do'nt know if it is different from xp-home(in asigning drive letters) but from my reading...no matter what I do in bios will not force windows to asign the drive letter C to a sata drive...maybe I'm wrong but even if I am I still think my issues lie elsewhere.
wj

sjj1805 · Post by **sjj1805** » Sun May 21, 2006 1:08 am

Heres one way of assigning an XP Drive letter:
http://support.microsoft.com/default.as ... 44&sd=tech

The way I do it is to right click "My Computer" on the desktop and select "Manage"
Then select "Disk Management"
Right click the drive that you want to assign the drive letter to
then select Change Drive Letter and Paths.
However as far as I am aware you cannot alter the drive letter of the one containing the operating system.

If you are stuck with Drive H then perhaps you could create a small partition and assign that the drive letter C. Then install the software onto C.

It might or might not work because having the operating system on H also means that various other folders are going to be stuck on H such as the
system32 directory and others.

keenart · Post by **keenart** » Sun May 21, 2006 3:16 am

The reason I say "do it all again" is very fundamental. Like Devil an old programmer, three computers, with many hard drives, and multi-boot installations.

I can assure you, when the registry gets damaged you are out of luck. This is a frequent occurance when you install two different versions of the same makers software and then uninstall one. Only to find that now nothing works. You will not find the damaged keys. Neither will Registry Mechanic or any other Utility. I have been through this a hundred times in past. This no longer happens since I make a Partition backup of every drive each week.

Sorry this is a fact of life. If I had the money I would buy Microsoft and turn all of the code into Open-Source.

sjj1805 · Post by **sjj1805** » Sun May 21, 2006 10:10 am

Please view:
http://phpbb.ulead.com.tw/EN/viewtopic. ... 5506#65506

Devil · Post by **Devil** » Sun May 21, 2006 11:17 am

I see 2 separate issues here.

1. Boot drives

I have used multi-boot on internal IDE drives and have never had a problem. I'd be hesitant about using swappable drives, though, for booting, a) because the registry can never be sure that it is relevant, as you may have changed something it refers to elsewhere, especially with hot-swappable drives; b) because you will inevitably reduce the performance of the computer if the cabling is different from standard.

Never, ever, use anything but IDE, SCSI or SATA for boot drives.

2. Partitions

On one computer, I have 4 partitions on Drive 0. There is a system on each of the first two partitions and a swap file for each on the other 2. On the other 2, I have booting on partition C: only. Apart from the system, the ONLY objects on the 4 boot drives are a) the essential drivers for the computer, b) utilities relative to system maintenance. I NEVER allow either data or applications on boot drives. I always move Mydocs off the boot drive, so that nothing is lost if I have a system crash requiring a re-partition, re-format or replacement of the boot drive. My applications, including all Ulead products, always go into partition D: which is in Drive 1. Data (except video) go into partition F:, also on Drive 1 (Drive E: exists on only one computer and contains only software relative to the Internet, which is the only one which has access- browser, e-mail client, firewall, anti-virus, anti-malware, POPFile e-mail sorter, FTP client). Drives 2 and 3 are only on the video computer for video data, swapfiles etc. I have a few other partitions for specific purposes on the non-video computers.

I'm sorry, Steve. I disagree with you about installing all the apps on the C: drive (Drive 0). I always have them on D: drive on Drive 1 and have never had any problems, not even with PI 11 (nothing to do with the PI11s in spamware!). As they are both Masters on IDE 1 & 2 (one SATA), it means that they can work simultaneously with much less drive wear (no head shuttling), with a distinct performance bonus (especially when the swap file is used).

As for uninstalling, I semi-manually remove as many registry entries as poss at the same time, using the powerful search feature in Registrar Lite. Registry Mechanic and suchlike do not cut the ice; you're lucky if they remove ½ of the entries and RM can cause problems (happily it automatically backs up!). I consider it essential to keep the registry free of unnecessary junk and junk keeps getting there, no matter how you try to avoid it. For this reason, I bite the bit yearly and reformat Windows boot partitions. Yes, it's a two-day job getting everything working again, but it's worth it.

This credo is probably why I rarely have software/hardware conflicts and all the apps run as smoothly as the authors allow. I have about 10 Ulead apps on my video computer and have never had any of the problems I see on the forums re crashes, conflicts etc.

wymjym · Post by **wymjym** » Sun May 21, 2006 1:55 pm

I'm saddened to think that my new machine, which has been up and running for two months needs to have the os re-installed and all programs added reconfigured.
Since....Ulead PI is the only one (so far) that does not function.

as much as I desire to have it functioning, I cannot in right mind go through the entire procedure knowing that there is just as good a chance that the same hiccup can/might/will occur.
I guess back to either finding the real issue(s) or as I indicated earlier, running a virtual machine with just UL-PI installed.
thoughts?
wj

sjj1805 · Post by **sjj1805** » Sun May 21, 2006 2:38 pm

There's obviously some misinterpretation of what a hard drive caddy is.
I think this picture should make it a bit more clear. It is in fact no different to taking the lid off the computer unscrewing your hard drive and then screwing another in its place. You have the system BIOS set to auto detect your hard drives and so it matters not that youve just swapped drives.

In fact its like having a collection of computers, only difference is they all share the same case!

Again do not confuse hard drives in caddies with external drives such as USB or Firewire - they are a totally different kettle of fish and in my opinion unreliable.

I didnt say installing on a different partition WILL create problems I said that installing onto a different partion CAN create problems.

To expand on this statement:
Computer programs are written by people.
We rely upon those computer programmers taking into account a variety of matters including the fact that an end user might choose to install to a drive other than the default C drive. Most but not all programmers take this into account.

This reminds me of the two years that I was a member of a group of people comprised of Senior members of various Local authority Departments, The Police, Fire Brigade and Ambulance services, plus a number of Large Private Sector Organisations considered to be at risk.

This was in relation to what was termed "The Millenium Bug."
Problems that would have been caused due to the Millenium Bug had it not been for 2 years of research and re-progamming of a variety of computerised services included lifts, traffic lights, electricity supply, water supply, street lighting and a whole host of other like systems.

The Millenium bug was largely due to early day computers having limited amounts of hard drive and/or RAM and so using 2 digits to represent the year instead of 4 was at the time a big saving.

Suprisingly though even when the RAM/Hard drive etc limitations were no longer an issue, many computer programmers still failed to take into account the imminent arrival of the year 2000.

The same is true of computer programmers failing to take into account that not everyone will install to their default C drive.