On Mon, 14 Feb 2005, RsH wrote:
> No drive C, but I [temporarily] renamed drive D to drive C, installed
> the program, rebooted and renamed C back to D, rebooted again as
> required and then moved the msmd6.dll file to Drive F, where it is now
> residing. Then the program works.
In future, if you need to fake a C: you can do the following:
- Open a command prompt (run cmd.exe)
- Enter: subst C: F:\
Now any references to C: is the same as a reference to F:. This will only
be true until you reboot your computer.
> That file turns out to be a small file which is their security [number
> of uses] counter. When the value gets to 30 it stops the trial from
> working any more, so they insist that the file be installed. Of course
> once you realise what this file is for, anyone with a Hex editor can
> negate this sort of check in an instant, by changing the value back to
> 1 or 0 and starting all over. The program does NOT handle conversions
> between volume and weight all that well, and is not nearly as flexible
> as MasterCook, in my opinion, so I likely will NOT keep it around, but
> at least it is now installed and usable.
>
> I still think that the programmer(s) have a poor install system if
> they insist on drive C as they have for this one file, instead of what
> the system actually has.
Any time a programmer has hard coded something like the System Drive or
anything else it is a clear indicator that the program lacks some
fundamental knowledge. Most often this is because they are self-taught and
use the trial-and-error method of learning.
I'd avoid using software from this sort of programmer. These are the type
who learn from mistakes and rarely from research. Often their mistakes are
reported by the people using their software. In other words, if you buy
their software you are basically paying to be their beta-testers.
> Anyway, thanks for the question, as it allowed me to remember the way
> to change a drive's letter value (other than the boot drive) so that I
> could D to C and then change it back and not screw up the programs
> installed on D and in the registry that way.
>
> RsH
> ---------------------------
> On Mon, 14 Feb 2005 00:52:20 GMT, Dave Bell
> > wrote:
>
> >RsH wrote:
> >> On my notebook my boot drive is drive F and NOT drive C, as I suffered
> >> a hard drive crash and when I switched to the new drive and installed
> >> windows on it XP's install and the hardware decided my boot drive
> >> would henceforth be drive F. Their trial software will NOT install or
> >> run if the boot drive is NOT drive C. They have hardcoded, in it, that
> >> one file, msmd6.dll, must be installed on c:\windows\system32 and, of
> >> course, my system does not have that at all, so the file, which is
> >> required, is not installed. I have written them about this problem and
> >> await their answer.
> >>
> >> Apparently Top Spin managed to install that one file, so if he cares
> >> to send me a copy privately [as an attachment] I will install it on
> >> drive F and let you know my view of the code.
> >
> >I understand that you boot on the F drive, but do you have a C drive
> >still? If so, you can simply create that directory structure on it, and
> >copy the required dll from F:...
> >
> >Dave
>
> ================================================== =====
> >
> Copyright retained. My opinions - no one else's...
> If this is illegal where you are, do not read it!
>
--
Send e-mail to: darrell dot grainger at utoronto dot ca
|