Dave-H

Win2000, you are absolutely right! I missed that last vital step. IT WORKS!!! You are a genius! Thank you so much.

Hi again, I found what my main problem with installing QuickTime 7.5 was! There is a file in the install package called "QuickTimeInstallerAdmin.exe" as well as the msi installer file. I hadn't copied that to the folder I was running the installer from, and it seems that it won't work without it! Anyway, the installer now completes, and asks for a function in shell32.dll. Running KDLLINST.EXE in Ez Install mode fixed that of course! I now have shell32.dll and shell2k.dll in the QuickTime folder. The "ExcludeFromKnownDlls" registry key now contains - kernel32.dll user32.dll shell32.dll ole32.dll advapi32.dll ws2_32.dll rpcrt4.dll imagehlp.dll msvcrt.dll comdlg32.dll All very encouraging, but unfortunately QuickTime still doesn't work! When I run it, an error message pops up saying - "QuickTime failed to initialise. Error # - 2096. Please make sure QuickTime is properly installed on this computer." Also, if I look at the QuickTime control panel, it tells me that I have version 0.0! The file types and mime types windows are empty. Also if I make any changes in the control panel they are not saved. If I run "QTInfo.exe" it says that QuickTime is "Not Installed"! So it obviously hasn't actually installed properly, even though the installer said that it had completed successfully. I've tried doing repair installations, and although they apparently complete successfully, they make no difference. I did some research on "Error #2096" and what came up was a problem with running in "compatibility mode" and says to switch compatibility mode off by changing the setting in the compatibility tab on the .exe file properties. Well, there is no compatibility tab in the exe file properties, is that a Windows XP only thing? Also there was some references to Error 2096 referring to an "unsupported processor". Is that really likely (I run on dual 2.4GHz Zeons)? When I clear the QT error message, I then get a message (from Norton Crashguard) about a crash in "GDI+ Window". I don't know if that's any clue........... Any suggestions? Thanks again.........

I've tried that, and everything seemed to do what it should do. Your shell32.dll and shell2k.dll are in the Quicktime folder. The "ExcludeFromKnownDlls" registry key contains kernel32.dll, user32.dll, shell32.dll, and advapi32.dll. Still getting the same error message when the installer runs. The "QTInstallCode.log" says - QuickTimePreInstallProc Enter Moving QTPrefs file (if necesary) to new location... Getting QT preinstall info... Getting QT process count... Ignoring process 'msiexec.exe' as possible QT process... Ignoring process 'msiexec.exe' as possible QT process... Ignoring process 'msiexec.exe' as possible QT process... Current QT processes = 0 GetQTProcessCount() reported 0 QT active processes. Will check for QT version: 7.50.61.0 QT DLL path: "C:\W2K Program Files\QuickTime 7\QTSystem\QuickTime.qts" Installed QT DLL "QuickTime.qts", version = 7.1.6.200 GetQTInstallInfo: Older QuickTime installed GetQTInstallInfo: is QTPro - yes, upgrade would invalidate - no Final result: 3 (error=0) QuickTimePreInstallProc Exit (error=0) Any more ideas? Thanks, Dave.

Hi win2000. Just tried installing Quicktime 7.5 following the above, but when the installer ran, after telling me which folder it was going to install to, it just went to the following error message, and wouldn't go any further. I tried again after using ez install to put your shell32.dll into the folder, but it didn't make any difference when I tried to install again. Any idea what's wrong? Thanks, Dave.

Hi win2000, Does this work if you use KDW in "EZ" mode, or do you have to actually replace the system files? Thanks, Dave.

You're right of course, 7.1.6.200 is the last official version of Quicktime for Windows 2000. That'll teach me to post things just from memory! That's the version I have, and it works absolutely fine on my system. I have tried the KDA system in system file replace mode, and abandoned it because it caused problems as previously mentioned. What I haven't done yet is try it in "EZ Install" mode, where it just uses wrappers i think and doesn't actually replace the system files. I'll let you all know how I get on!

Well I tried the KernelEx suggestion, but I'm afraid that installing it made no difference. I'm sure it's a good thing to have it installed anyway, so thanks RetroOS! I then looked at Problemchyld's suggestion of substituting files from the older version. There doesn't seem to be a file called "directx.cab". There isn't one called "bda.cab" either. There are files called "bdant.cab" and "bdaxp.cab" though. Are you seeing different files from me Problemchyld? Well, to cut a long story short, from my experiments with substituting files, the files causing the problem turned out to be "dxupdate.cab" and "dxdllreg_x86.cab". If the 2008 version of either of those files is present the installer fails. If I have all of the 2008 files in the folder except those two, which I substitute with the 2007 versions, it works! dxdllreg_x86.cab contains two files, "dxdllreg_x86.inf" and "dxdllreg.exe". The inf files are identical in both versions as far as I can see. The dxdllreg.exe files claim to be the same version (4.9.0.0904) but are of different file sizes. The 2007 one (65KB) has a digital signature, the 2008 one (79KB) doesn't, rather surprisingly. dxupdate.cab contains three files, "dxupdate.inf", "dxupdate.dll", and "dxupdate.cif". The dxupdate dlls again both claim to be version 4.9.0.0904 but are of different file sizes. The dxupdate.inf files are different. The 2008 version has entries added under the [DirectX_Update_PlugIn] section for Nov 2007, March 2008, and Jun 2008 cab files. Not unexpected of course. The 2008 "cif" file likewise has entries added for these new cabs. It's probably the calling of one or more of these new files that's causing the problem of course, which is why the 2007 version of "dxupdate.cab" works, because it ignore them! Still puzzled about "dxdllreg_x86.cab" though......... I did get some entries this time in my error log files when the install failed. DxError.log records - -------------------- [08/08/08 22:31:06] module: dxupdate(Jul 20 2007), file: dxupdate.cpp, line: 1091, function: CabCallback SPFILENOTIFY_FILEEXTRACTED: error = 13. -------------------- [08/08/08 22:31:06] module: dxupdate(Jul 20 2007), file: dxupdate.cpp, line: 5665, function: DirectXUpdateInstallPlugIn Failed API: SetupIterateCabinet() Error: (13) - The data is invalid. Unable to iterate through C:\WIN-98\TEMP\dxdllreg_x86.cab. The file may be damaged. -------------------- Anyone any ideas?

There's more about this here - http://www.msfn.org/board/KDW-FCWIN2K-t120936.html This is a message from the guy in Japan who developed KDW. I was getting that "broken backup" message too, but only after I did the EZ Install, not the full setup, which seemed to work OK. I think that the third path down at the top of the program's window, which starts off blank, is where you put the path for it to put stuff when using the EZ Install mode. If you don't put anything in there it seems to put extra files into the folder which KDLLINST.EXE is being run from. Certainly I never got rid of the error message until I manually deleted those files. I'd try deleting all the files in the folder that you unzipped KDW to, and then start again. The thread mentioned above says that you have to check "EZ KD Registry" before you run the install if you're using that mode. I'm afraid that I couldn't work out what that does! I do hope that this gets better English documentation soon......... To run the thing in full mode, you have to uncheck "EZ KD Registry" and select all the system DLLs until they all say "standby". Then hit "Start Setup". It should then show you what it's doing, replacing the files, and prompt for a reboot. At this point, cross your fingers and do it! Good luck........

Welcome! You could try using the "full" mode on KDA, and if it's successful try the hacked installer again. I would strongly advise backing up your system first though, as some systems will not start if the system files are replaced. I won't take any responsibility for this! I have a dual boot system, so I just made a backup of my Windows 2000 (WINNT) folder using Windows 98. Fortunately I didn't have to use it. Mine did restart OK in fact, but there were a couple of other annoyances that made me go back again (see "the KernelEx for 2000?" thread for the details.) If it reboots OK after the KDA install, but you want to roll back anyway, the uninstall mode seems to do a good job of restoring the old system DLLs correctly. Good luck!

I did install 7.2.0.240 on Windows 2000 successfully after modifying the installer, but the full screen function didn't work properly. The on-screen controls refused to go away after the preset delay as they're supposed to. The only workaround was to switch them off altogether! So I went back to 7.1.4. The KDA utility you need is FCWIN2K.EXE, which is included in the package. There's a link to download it earlier in this thread.

AFAIK you will still need to hack the installer file, as I don't think that installing an API extender will fool the installer's OS version check. I extracted the Quicktime msi file from the installer exe package using uniextract, and then modified the msi using the KDA utility. Unfortunately, it still didn't work! I also tried with Orca (another msi editor) with the same result. It would go through the motions of installing, with no error messages about the OS version, but then stopped with an unspecified error. I may try again sometime, but too busy with other things at the moment! Does Quicktime 7.5 have any great advantages over 7.1.4, which was the last version officially compatible with Windows 2000? I have the "pro" version of 7.1.4, so the main new advantage on the 7.5 free version, full screen playback, I have available anyway.

Never much love for Mr. Norton is there! It's true that a lot of Norton Utilities are of questionable benefit, and some of the things that they recommend that you run all the time are like hanging an enormous millstone round the neck of your computer! Those that are good are good though, and the Protected Recycle Bin has saved me on many occasions when I've deleted something and then emptied the Recycle Bin, and then changed my mind (we've all done it!) Also it saves overwritten copies of documents which are being modified by applications, and image files. For instance, if I'm editing an image, sometimes I'll press save and close it, then realise that I want an earlier version back. If I'm in luck, Norton will have saved it, and I can use Norton Unerase to retrieve it. So, I would miss it! Anyway I've now restored the system to normal. I looked into running KDW in "Ez mode", which doesn't actually replace the system files in the System32 folder, but appears to use the same method as the "Windows 2000 to Windows XP API Wrapper Pack" previously mentioned. Haven't got very far with it as yet though.

That doesn't sound too bad actually, and quite a clever idea. Almost makes me think of going to Vista. (I did say almost!)

Well, tried it tonight, and in fact it seemed to work fine. Replaced all the system files with the new versions, and the system rebooted fine, with no BSOD. How it got round the System File Protection is anyone's guess! I did have two consequential problems though. Firstly, I was immediately nagged by Windows Update to install the last cumulative security update for Internet Explorer. KDW had replaced some files such as SHLWAPI.DLL which are part of those IE updates. As it was seen as an earlier version the update was flagged again. Also, I have Norton Utilities (2002) installed, which includes a utility called "Norton Protected Recycle Bin". I started getting error messages on boot-up that the Norton Protection service couldn't start because it couldn't determine the operating system version. Another consequence of the system files replacement I assume. The only reason I wanted this really was to install Quicktime 7.5. In fact even with the new system files, and hacking the MSI file using the KDW utility (or indeed with Orca) it still wouldn't install, with an unspecified error. I've decided to leave things as they are. I was pleased to find that the KDW uninstall routine did seem to do its job, and restored all the system files so my system seems to be back to as it was before.

Thanks for that. Sounds like I'm wasting my time even investigating this, which is good to know! I won't bother taking it any further. Interesting about the Vista "suspend-to-RAM" recommendation. If that really is what MS recommend instead of shutting down properly, that doesn't sound very environmentally friendly. So much for Microsoft's "green" credentials!

I'm very interested in this too, and I'm going to try it out over the weekend. I'll let you know if I hit similar problems! I'm going to completely back up my Windows 2000 folder first.................

Indeed it is, but I do remember reading somewhere that MS had changed the startup routine in XP to make it start up faster, which is why the ntldr from XP could be used on 2000 to get at least some of the benefits of this. This is something I've never been able to try out, for the reasons given in my OP, so I've no idea if it works, and how much effect it actually has if it does work!

Shockwave 11 in my experience doesn't even work on Windows 2000, let alone Windows 98!

Just tried that, extracting with Universal Extractor. Exactly the same result. an "internal error" message when dxsetup.exe scans for items to update. Very strange, whether it's necessary or not, I still don't understand why this package won't install on an operating system that it says that it's compatible with!

I have .NET Framework 1.1 installed, and the update still won't work for me. I did have 2.0 installed as well, but I removed it to clear the registry a bit. I doubt if that has caused the problem though.

Indeed not, Windows 98FE is the earliest OS quoted on the MS download page.

Thanks very much, let me know how it goes. I still don't understand why we are having problems with this upgrade, when MS clearly state on their download page for it that it is compatible with Windows 98! I could understand it if one of the unofficial upgrade patches had broken compatibility, but if it won't install on a clean new vanilla install of Windows 98 that is really puzzling.

Thank again RetroOS! I found a copy of ADVAPI32.DLL version 4.90.0.3000 and put it in my windows\system folder. Unfortunately, still no difference! I'm still getting exactly the same error message when I run dxsetup.exe. I tried the version from my Windows 2000 installation too, which is 5.0.2195.7038. Windows 98 wouldn't even start with that installed, just BSOD........... Incidentally, the 98SE2ME pack doesn't actually seem to include the ADVAPI32.DLL file, it seems to assume that you have a Windows ME installation disk, which I haven't! Any more ideas.................?

Soporific, does AP June 2008 contain the June 2008 Update to DirectX 9.0c Runtime? The reason I ask is because I've been having trouble installing it (see here) This hasn't been resolved as yet, and I was hoping that AP might succeed where the normal install routine is failing! Thanks, Dave.

I have dual booted Windows 98 and Windows 2000 for years now. I've never had any problem with keeping FAT32 drives. Being able to repair one operating system using the other has always been one of the main advantages IMO.