Re: [smartmontools-support]Fw: SmartMonTools 5.33 - "Not a valid

[Eric P. <pra...@ec...>]

 
Some follow up on this.

I installed 6 machines with an identical image of Win XP SP2.

My MSI of SmartD would not start on any of them.

I took an MSI I'd made from the same machine with Win XP SP2 and it also 
failed to start smartd as a service claiming "not a valid Win32 app".

I then took a machine, and used WinInstallLE - the program which we use to
generate MSI install files.  It does a diff of the harddrive and registry.
I used that to diff what happened when I ran:

	smartd remove
	smartd install

I recieved no useful information (the usual noise I get from Windows and other
tasks running.

So - I'm not sure what the @#$#@$ is so special about SP 2.

Yes if I _MANUALLY_ install it it'll work fine.
But when it's pushed via an MSI install as per Windows Domains with Windows
controllers and Windows clients - it just doesn't start.

If anyone has any clue I'd gladly test some things out.  It takes me about a
working day to create the MSI's and test them though.  So it's not easy to do
and I can't think of any easy way to test this.


 - Eric
 
> >> But it was to report that with Win XP - when SP2 is applied - SmartD no
> >> longer starts as a service due to the error "not a valid Win32 app".
> >>
> >> But I can start it as admin.  A web search reveals that other software
> >> is hit with this problem - but I found no solution.
> >
> 
> I could not reproduce this and have no idea why this might happen, sorry.
> On the XP SP2 systems I tested, smartd 5.33 works fine.
> 
> When (registering service, starting service) and where (Messagebox, 
> eventlog) does the error message "not a valid Win32 app" appear?
> 
> This error message usually occurs if the .exe is broken.
> But if you can start the same smard.exe from the command line, the .exe 
> itself should be OK.
> 
> Just to be sure, here the md5 checksums for the files from the 5.33 
> windows distribution:
> c8fd25a10911f8811003aa6bfda61203 *smartctl.exe
> 858e1bd49e6c9b82b736106671c03c06 *smartd.exe
> 70019a0be70fa69f01c3bc8bc0294a03 *syslogevt.exe
> 
> Did you try to reinstall the service registry entry for smartd ("smartd 
> remove", "smartd install [options]")?
> The SP2 upgrade may have modified it for some reason.
> 
> 
> >> Note that I've only tried about 5 machines with SP2 so far and it did 
> >> work
> >> on one of them!
> >
> 
> Are there any obvious differences between the 4 non-working and the one 
> working machine, especially regarding security items like virus scanners?
> 
> 
> >> In 2 weeks we deploy SP2 and I'll have hundreds of machines that may 
> >> not be
> >> running SmartD.
> >
> 
> Be sure to check your mission critical apps before. [At my real job we 
> have a legacy app that was built with IBM Visual Age. It runs fine on 
> each windows flavor so far, except on XP SP2 it crashes during startup 
> in one of the VA C++ runtime DDLs. VA was discontinued in 2001, so we do 
> not expect any patch ;-[]
> 
> 
> >> It's a great tool - I installed it and nailed a good 16 drives that 
> >> were on
> >> their way to failure - luckily 1 week from when many of them went out 
> >> of warranty.
> >> None of them hard started corrupting data yet - so the usefullness 
> >> was quite apparent.
> >
> 
> Thanks!
> 
> Christian
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Smartmontools-support mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>