Installing Trend Officescan Client

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I am building a basic terminal server client machine which I want to have as small a footprint as possible. Everything so far works perfectly with the exception of installing my antivirus software, Trend Officescan. A colleague has built another embedded image which Trend installs on fine; however the size of the build is just over 300Mb, which is too large. I can't seem to figure out what the difference between the two builds are which would get trend to install.

Thanks in advance for any help anyone can give on this problem.
 
Petey,

I haven't played with the Trend Officescan on XPe.

Can you provide us with a bit more information so that we could help you.
How do you "install" the software?
What errors do you see?
Anything related in setupapi.log?

--
Regards,
KM, BSquare Corp.

Hi,

I am building a basic terminal server client machine which I want to have as small a footprint as possible. Everything so far
Click to expand...
works perfectly with the exception of installing my antivirus software, Trend Officescan. A colleague has built another embedded
image which Trend installs on fine; however the size of the build is just over 300Mb, which is too large. I can't seem to figure
out what the difference between the two builds are which would get trend to install.
 
The installation is from our trend antivirus server where we run the installation. The install starts and then just stops after a couple of seconds with no error messages or any other info. Trend also provides a utility to package the install for deployment which I have done. This does give an error which is that the application "is not a valid win32 application".

Where can I find the setupapi.log file?
 
Petey,

The installation is from our trend antivirus server where we run the
Click to expand...
installation. The install starts and then just stops after a couple of
seconds with no error messages or any other info.

Make sure you have satisfied all the application's dependencies. Use
Depencency Walker (better 2.0) on all app binaries available and then TD
File Filter feature to find out all the components you need to include to
your image.
Use Regmon/Filemon tools from www.sysinternals.com to monitor what's going
on in the system while you are running the install.

Trend also provides a utility to package the install for deployment which I
Click to expand...
have done. This does give an error which is that the application "is not a
valid win32 application".

Include "Dos Windows on Windows Support" component.
Where can I find the setupapi.log file?
Click to expand...

\windows\setupapi.log. Although, it seems you may not have related errors in
the file. Anyway, never hurts to take a look.

KM
 
Back
Top