11 replies to this topic

[piemai]

Fresh Installation of Windows XP SP3 Dual booting with a RC of Windows 7.

Have a copy of autopatcher with all current x86 windows xp updates, directx, .net, addons, java...

When i go to run autopatcher.exe nothing happens...

I have already installed the visual basic 6 runtime package (vbrun60sp6.exe)

Tools/editor.exe runs fine

i have also tried copying most of the files from /bin to system32, registered them with regsvr32

Running the same autopatcher.exe from windows 7 has it starting up... i have also installed windows xp sp3 into a virtual machine and am getting the same results there....

The copy of windows xp had SP3 slipstreamed using nlite.

Any thoughts?

Not being able to use autopatcher is really frustrating.

[Cristiano]

the current version of autopatcher.exe is unable to recognize windows seven rc properly. in order to run it properly under seven, the .exe himself has to be updated. it may be fixed with the rtm version, but further tests will be required. but even with that limitation, autopatcher runs under seven. windows xp versions made by nlite us to be problematic. the issue comes with the components that can be removed from the installer. some are needed by some softwares, despite lack of knowledge of some people and, due that, the windows made with that can have certain issues with certain softwares that require the removed component. did you removed any component of windows when running nlite? also, autopatcher has certain issues with the full patch. just imagine that you are running autopatcher from desktop and your user is "years & years". then, the full patch will be C:\Documents and Settings\years & years\Desktop and, due that &, autopatcher may not run. the same thing when the patch has ç ã é, ô and other kinds of non-english characters.

at this point, i may grant you that autopatcher works fine with untouched versions of windows xp and system languages (i've already tested it under several languages already). autopatcher also works under sp2/SP3 nicely. issue: currently, certain anti-virus softwares has some false-positives to some dlls (more details into announcements) and, if you have any of those that has those issues, they may prevent autopatcher from run.

to more details about, we need to know where you are running autopatcher from (full patch, please), anti-virus software and language (some languages also have issues with autopatcher) and more details that you think relevant. also, you may look under windows folder for an file named autopatcher.log. if that file is in there, please open it with notepad and paste the entire content of it in here

thanks

[]s

Edited by Cristiano, 05 August 2009 - 02:37 PM.

[piemai]

Sorry to post duplicate post, this was an accident due to sleep deprivation...

Attached Files

•  LAST SESSION.TXT   8.92K   4 downloads

Edited by piemai, 05 August 2009 - 03:47 PM.

[piemai]

First of all, thank you so much for taking the time to reply

I am running autopatcher from the path i:/autopatcher
this is a partition i use for installers

Language is English and there is currently no anti-virus on the system.

As for nlite, I have been creating custom windows CDs every couple of months since late 2005... i am usualy very careful about what i change and remove... here is a summary of what i changed in this windows disk and attached is the last_session.ini from the disk

-Removed following componants: MSN Explorer, Windows Messenger, Tour
-Slipstreemed Service Pack 3
-Critical patches to june 2009 (xable's update pack)
-Windows media player 11 and IE8 added
-Changed some defult services (only after reading up on each service i changed http://www.blackvipe.../servicecfg.htm)
-Added several other themes to windows and applied uxtheme patch
-Numerous Tweaks of the UI (all listed in the .txt)
-Made portions of the installer Unattended

I have also been using autopatcher for a long time and have never had it refuse to run on a fresh install of windows before... i accept that along the way somewhere i have done something wrong when creating the nlite disk... i would love to know exactly what i removed or disabled that autopatcher is dependant on.

here is a copy of the autopatcher.log

AutoPatcher 5.6 loaded the filesystem.

Detected English (1033) Windows XP Professional Service Pack 3

System Components:
	Internet Explorer: 8.0.6001.18702
	Windows Media Player: 11.0.5721.5145
	.NET Framework: 
	Windows Installer: 3.1.4001.5512
	DirectX: 4.09.00.0904
	MSN/Live Messenger: 

Office Components:
	Microsoft Word: 
	Microsoft Excel: 
	Microsoft PowerPoint: 
	Microsoft Outlook: 
	Microsoft Access: 
	Microsoft Project: 
	Microsoft Publisher: 
	Microsoft OneNote: 
	Microsoft FrontPage: 
	Microsoft InfoPath: 
	Microsoft Visio: 
	Microsoft SharePoint Designer: 
	Microsoft Groove: 

Again, thank you for your time...

Attached Files

•  LAST SESSION.TXT   8.92K   1 downloads

Edited by piemai, 05 August 2009 - 03:51 PM.

[Cristiano]

humm... this "i:/autopatcher" is an remote folder? if is, this may be the cause. there's one way to bypass that, but i don't remember right now (i'm fighting to keep awake, after my lunch...)

by the way, looking into your last session log, i may have noticed (i'm fighting to keep awake...) an know issue regarding nlite. you can't integrate service packs and do other tasks at same time. this is too risky.

[]s

Edited by Cristiano, 05 August 2009 - 05:39 PM.

[piemai]

i:/autopatcher is stored locally

I think I'm going to call it a night for now... (its nearly 4AM here and i am also fighting to stay awake)

Thanks for your input.

[James]

Piemai, can you confirm whether this affects just autopatcher.exe, or does it also affect apup.exe?

What do you have your Language for non-Unicode programs set to? (See the topic APUP Frequently Asked Questions (APUP FAQ) at question 13 for details of what I mean.

Can you confirm exactly which files from the bin folder you have registered, please?

Usually, you should copy the four .OCX and four .DLL files from AutoPatcher's BIN folder to SYSTEM32.
After that, you should register (with REGSVR32) the four .OCX files and also FM20.DLL and SSubTmr6.dll (total: 6 files to register). Do not attempt to register the other two DLL files, because they are not designed to be registered.

If you have done something different, please let us know.

==

[piemai]

this issue only seems to effect autopatcher.exe

apup.exe and tools\editor.exe start up fine

Language for non-Unicode Programs is English (United States)

I have copied the following 6 files to system32 and succuesfully registered them using regsvr32
(COMCTL32.OCX, COMDLG32.OCX, FM20.DLL, MSCOMCTL.OCX, RICHTX32.OCX, SSubTmr6.dll)

[piemai]

Problem solved....

I have DEP (Data Execute Prevention) set to opt out...

For some reason autopatcher seems to conflict with DEP...

Autopatcher.exe runs just fine after adding it to the exceptions list.

If anybody has any questions, or if i can be of any assistance to help solve this DEP conflict just let me know how i can help..

I have been a user of autopatcher for years now and i simply love it. No other tool has saved me more time, energy, downloads and allowed me to ensure an up to date operating environment right from the start.

Again, thank you to everybody that gave me ideas and input... I really appreciate it.

[piemai]

Further information... screen captures of error taken in the VM... (i had error reporting service disabled in windows so it never told me DEP was preventing autopatcher from running)

Adding autopatcher.exe to the exclusions list for DEP fixed the problem both in the virtual environment and on the separate physical machine.

Edited by piemai, 06 August 2009 - 11:52 AM.

[James]

Thanks for the additional information and thanks for letting us know that you have solved the problem.

That looks like a "Memory Access Denied" error in the Error Signature parameters, given in the screenshot, which confirms that AutoPatcher.exe must be run with DEP turned off.

==

[Cristiano]

> AutoPatcher.exe must be run with DEP turned off.
i always run autopatcher with dep in default mode, aka enabled. and it works

[]s