Neal: Problem Worse Than Thought

[rename]
NUL=C:\WINDOWS\TEMP\GLB1A2B.EXE
Mike: The above 2-lines are what I got last time after
opening wininit.ini in Notepad. I see GLB1A2B.EXE in
Explorer C:/Windows/Temp as 161KB Application 9/28/2001.
This apparently is the only "wininit" source. What next?
-----Original Message-----
Is it the same entry each time? If not please reboot a
few times and copy
the entries into your reply. Personally I suspect malware
as being the
cause despite your having used AdAware, Spybot S&D, BHO
Demon, Spyware
Blaster.

As for why cut and paste doesn't work on your PC I have no
idea.
Control+A = Select All, Control+C = Copy selected text to
clipboard,
Control+V = Paste contents of clipboard to cursor position.
--
Mike Maltby MS-MVP [2001-2004]



Craig S wrote:

Just Sent Reply without my Sender's name-This is Duplicate.
[rename]
NUL=C:\WINDOWS\TEMP\GLB1A2B.EXE
Opened wininit.ini in Notepad and just copied; Cntrl A/C/V
cmmds didn't work; Advise what to try next if this helps!

.

I still suspect that your problem is due to your having malware. There is
no other reason why you should otherwise be using the wininit.ini
mechanism to delete an executable file from your temp folder each time
that you boot your system. If it isn't malware then it has to be due to
some application or other that you have installed. Looking at the
properties of this file might give you a clue as to its origins. Knowing
that information then using MSConfig | Startup have a look at what you
have being loaded each time you boot your PC that does not form part of
the underlying operating system.

Cancel that!

OK, some research using Google shows that GLB1A2B.EXE is due to the
operation of the Wise installer and GLB1A2B.EXE is a copy of unwise.exe.
This then raises the questions as to why the Wise uninstaller is running
each time you use your PC. Again I would look to MSConfig | Startup.
--
Mike Maltby MS-MVP [2001-2004]




wrote:

[rename]
NUL=C:\WINDOWS\TEMP\GLB1A2B.EXE
Mike: The above 2-lines are what I got last time after
opening wininit.ini in Notepad. I see GLB1A2B.EXE in
Explorer C:/Windows/Temp as 161KB Application 9/28/2001.
This apparently is the only "wininit" source. What next?
.

Mike: I found the AdAware connection when U did & have
posted the issue in the chat group. Tons of posts on
GLB1A2B.exe & too many to read. Will advise if I get help
so U can help others.
-----Original Message-----
I still suspect that your problem is due to your having
malware. There is
no other reason why you should otherwise be using the
wininit.ini
mechanism to delete an executable file from your temp
folder each time
that you boot your system. If it isn't malware then it
has to be due to
some application or other that you have installed.
Looking at the
properties of this file might give you a clue as to its
origins. Knowing
that information then using MSConfig | Startup have a look
at what you
have being loaded each time you boot your PC that does not
form part of
the underlying operating system.

Cancel that!

OK, some research using Google shows that GLB1A2B.EXE is
due to the
operation of the Wise installer and GLB1A2B.EXE is a copy
of unwise.exe.
This then raises the questions as to why the Wise
uninstaller is running
each time you use your PC. Again I would look to MSConfig
| Startup.
--
Mike Maltby MS-MVP [2001-2004]





wrote:

[rename]
NUL=C:\WINDOWS\TEMP\GLB1A2B.EXE
Mike: The above 2-lines are what I got last time after
opening wininit.ini in Notepad. I see GLB1A2B.EXE in
Explorer C:/Windows/Temp as 161KB Application 9/28/2001.
This apparently is the only "wininit" source. What next?
.

.

Craig,

I made no reference to AdAware (although I appreciate that it could pick
this up) but rather what is causing the problem, namely the Wise
installer. To try and summarise what happens is that to give the
impression to the user when uninstalling an application that all has been
deleted (which is difficult to do since unwise32.exe will be running as it
performs the uninstall), Wise copy unwise32.exe to the temp folder as
GLB1A2B.EXE and run that copy rather than unwise32.exe. This means that
al of the application being uninstalled gets uninstalled including
unwise32.exe just leaving GLB1A2B.EXE to be deleted after rebooting using
the wininit mechanism.

I therefore don't see what AdAware has to do with the problem, unless, of
course, it is AdAware that is using the Wise installer each time that it
is used.
--
Mike Maltby MS-MVP [2001-2004]



Craig S wrote:

Mike: I found the AdAware connection when U did & have
posted the issue in the chat group. Tons of posts on
GLB1A2B.exe & too many to read. Will advise if I get help
so U can help others.

Mike: Hope I have answer. The link
http://www.lavasoftsupport.com/index...l=glb1a2b\.exe
and last Post by Tech Support Guy and the link/4th post by
graustark
http://forums.net-integration.net/in...ic=20503&st=30
indicate that by DELETING THE ADAWARE DESKTOP SHORTCUT AND
RECREATING it from C:\PROGRAMS\LavaSoft the Problem
disappears. I did so, Cold Start/Search for wininit.ini =
nothing/Opened AdAware via Desktop NEW Shortcut, 2nd Search
and wininit.ini DID NOT APPEAR Tons of posts via Google
and I'll advise soon if Fix Remains. Thanks for all your
interest!!!!!

-----Original Message-----
Craig,

I made no reference to AdAware (although I appreciate that
it could pick
this up) but rather what is causing the problem, namely
the Wise
installer. To try and summarise what happens is that to
give the
impression to the user when uninstalling an application
that all has been
deleted (which is difficult to do since unwise32.exe will
be running as it
performs the uninstall), Wise copy unwise32.exe to the
temp folder as
GLB1A2B.EXE and run that copy rather than unwise32.exe.
This means that
al of the application being uninstalled gets uninstalled
including
unwise32.exe just leaving GLB1A2B.EXE to be deleted after
rebooting using
the wininit mechanism.

I therefore don't see what AdAware has to do with the
problem, unless, of
course, it is AdAware that is using the Wise installer
each time that it
is used.
--
Mike Maltby MS-MVP [2001-2004]



Craig S wrote:

Mike: I found the AdAware connection when U did & have
posted the issue in the chat group. Tons of posts on
GLB1A2B.exe & too many to read. Will advise if I get help
so U can help others.

.

Mike: Hope I have answer. The link
http://www.lavasoftsupport.com/index...l=glb1a2b\.exe
and last Post by Tech Support Guy and the link/4th post by
graustark
http://forums.net-integration.net/in...ic=20503&st=30
indicate that by DELETING THE ADAWARE DESKTOP SHORTCUT AND
RECREATING it from C:\PROGRAMS\LavaSoft the Problem
disappears. I did so, Cold Start/Search for wininit.ini =
nothing/Opened AdAware via Desktop NEW Shortcut, 2nd Search
and wininit.ini DID NOT APPEAR Tons of posts via Google
and I'll advise soon if Fix Remains. Thanks for all your
interest!!!!!
-----Original Message-----
Mike: Hope I have answer. The link
http://www.lavasoftsupport.com/index...l=glb1a2b\.exe
and last Post by Tech Support Guy and the link/4th post by
graustark
http://forums.net-integration.net/in...ic=20503&st=30
indicate that by DELETING THE ADAWARE DESKTOP SHORTCUT AND
RECREATING it from C:\PROGRAMS\LavaSoft the Problem
disappears. I did so, Cold Start/Search for wininit.ini =
nothing/Opened AdAware via Desktop NEW Shortcut, 2nd Search
and wininit.ini DID NOT APPEAR Tons of posts via Google
and I'll advise soon if Fix Remains. Thanks for all your
interest!!!!!

-----Original Message-----
Craig,

I made no reference to AdAware (although I appreciate that
it could pick
this up) but rather what is causing the problem, namely
the Wise
installer. To try and summarise what happens is that to
give the
impression to the user when uninstalling an application
that all has been
deleted (which is difficult to do since unwise32.exe will
be running as it
performs the uninstall), Wise copy unwise32.exe to the
temp folder as
GLB1A2B.EXE and run that copy rather than unwise32.exe.
This means that
al of the application being uninstalled gets uninstalled
including
unwise32.exe just leaving GLB1A2B.EXE to be deleted after
rebooting using
the wininit mechanism.

I therefore don't see what AdAware has to do with the
problem, unless, of
course, it is AdAware that is using the Wise installer
each time that it
is used.
--
Mike Maltby MS-MVP [2001-2004]



Craig S wrote:

Mike: I found the AdAware connection when U did & have
posted the issue in the chat group. Tons of posts on
GLB1A2B.exe & too many to read. Will advise if I get help
so U can help others.

.

.

That is one only cause of the problem. As I have previously stated and as
can be readily verified by using Google the more general problem is due to
the way that the Wise uninstaller works.
--
Mike Maltby MS-MVP [2001-2004]



Craig S wrote:

Mike: Hope I have answer. The link
http://www.lavasoftsupport.com/index...l=glb1a2b\.exe
and last Post by Tech Support Guy and the link/4th post by
graustark
http://forums.net-integration.net/in...ic=20503&st=30
indicate that by DELETING THE ADAWARE DESKTOP SHORTCUT AND
RECREATING it from C:\PROGRAMS\LavaSoft the Problem
disappears. I did so, Cold Start/Search for wininit.ini =
nothing/Opened AdAware via Desktop NEW Shortcut, 2nd Search
and wininit.ini DID NOT APPEAR Tons of posts via Google
and I'll advise soon if Fix Remains. Thanks for all your
interest!!!!!