Is ACMSETUP.EXE the only setup program? There should be a SETUP.EXE as well. I've noticed that with all Microsoft programs there are both of these files, I've never run the ACMSETUP.

Yes, I run setup.exe, go through the license menus, then it does nothing for a few minutes and announces "Acme setup not found" or some such. Acmesetup is obviously called by the setup program. From the Microsuck KB I have deduced that Acme is some sort of archaic installer service that precedes Windows Installer. The problem is that XP doesn't support anything before version 2.6.

Tried to run it in compatibility mode? Otherwise you're stuck with .NET, mwahahaha! 😜

Not sure what your problem is as I've got at least 4 machines running Windows XP with Visual Studio 6 installed...

The XP I have is a home edition upgrade from Me. Obviously there is a configuration issue, but if no one knows how to solve it, I'm stuck anyway.

Whenever I install Windows, I do a clear installation. Less comfortable, but more stable and it also takes less space (since there do not remain lying around any old things on harddisk)

Mirek

Since the upgrade and not the full edition of Windows was purchased, this is not currently an option.

I suppose I'll remember that for the next version of Windows...

don't upgrade
install it the way so that you have both systems (there is such an option when you begin installation - i think you have to tell the installer to install winxp on another partition - D:\ for example)
this way i have win98se installed on msdos6.2 and winxp installed on win98se. So i have 3 systems now on one hdd and i can choose which one to use when my computer starts.

I figure you probably have a combo ISA/PCI motherboard. I'm surprised there is a video card that works with both MS-DOS and windows xp

GeForce FX 5200 128MB
Nothing to be surprised at, every gfx card works in dos.

All video cards work with DOS 😮 You probably will not get the VESA modes that were common some years back but basic VGA is still a required standard as far as I know!

As for your original problem...

A MS support response offered this:

Try turning switching the Transfer Mode from DMA to PIO Only. […]
Show full quote

Try turning switching the Transfer Mode from DMA to PIO Only.

Device Manager
Expand IDE Controllers
Right Click on each of the IDE Controllers and go to properties
Select the Advanced Settings Tab
Change the Transfer Mode to PIO Only.

Microsoft support article of interest:
http://support.microsoft.com/?id=250343

If that doens't work, grab a copy of the Dependency Walker and verify that ACMESETUP.EXE uses this set of imports. Make sure all imports are able to be resolved without error:

1    kernel32.dll
2    advapi32.dll
3    user32.dll
4    gdi32.dll
5    ole32.dll
6    mpr.dll
7    mssetup.dll
8    shell32.dll

Check their versions, locations, etc.

Profile the application using Depends. Also grab File Monitor and track the ACMESETUP application for file activity. What you'll be looking for is a DLL load event that is failing. Either through a lack of a file or the specific resource from the DLL.

...and finally, why is this posted in this forum ?

"Try turning switching the Transfer Mode from DMA to PIO Only."

Hahahahahahahaha!!!!! "I'm sorry sir, but your HDD is too fast. Please downgrade." 😉

The hard drive advice is bologna. You have to force the install from the command line. The KB article had what I needed. I didn't find it before because I restricted myself to Windows XP articles.

Glad I could be of service to you Vlad.

Thanks Reckless. I tried various Microsuck newsgroups, and the DLTCEP forums where they write some MFC stuff. No one else had a clue.