Dave-H

Try this, as suggested on Win2000's blog. Run Win2000's WMP10 installer again. When the dialogue box "Detect Media Player 10, Delete it and continue?", comes up, hit OK. Let it finish, and then just cancel the install when the WMP10 installer splash screen come up. Worked for me, and I'm now back to WMP9 as before.

Meados I've sent you a PM with links to my Windows 2003 startup files. I just wish they worked for me! Jacobmax, thanks for the feedback. Are you saying that the entries in my boot.ini file do match my drive configuration? If so, we still don't know why these newer startup files won't work on my system. Ninho?

Thanks again Ninho! This is what my disk management looks like. Does it seem OK? I'm not sure how you determine whether a partition is "number 2" or not. The D: drive is certainly listed after the C: drive on disk 0, but does that make it number 2 or number 1 (C: being 0)? Thanks again for all your help. Dave.

Sorry for the delay in responding ninho. I have now checked the partitions on my system disk, which contains drives C: and D:. D: is the Windows 2000 partition. C: is an active primary DOS partition. D: is a logical DOS drive within an extended DOS partition on the same disk. So D: not a primary partition. I believe IIRC that you can only have one primary partition on a disk. Is that the problem?

Thanks win2000. Sorry to hear about the death of your PC. I hope you're up and running again soon! If you want to test AVS Video Converter you can download it here - http://www.avsmedia.com/videotools/download.aspx

Hi again Win2000, I've now got all my main system files replaced with your versions. I managed to fix the Norton problem by using your Ez Install mode and putting the older 5.0.2195.7135 kernel32.dll into the folder with the Norton executable files, with version 5.1.2599.28 of kernel2k.dll. That works fine. I now have another problem! I have AVS Video Tools 5.6 installed, and I use the video converter program a lot. It's supposed to work with Windows 2000 and XP. Now if I run it, I just get an error message - AVSMEDIA An internal exception occurred (Address: 0xb) Please, contact support@avsmedia.com. Thank you! This goes away and it works again if I put the original kernel32.dll back into my system32 folder. I have tried using the same trick as I did with the Norton utilities, but it won't work with this program. I can make the error message go away, the program runs and appears as a running task in Task Manager, but nothing ever appears on the screen. Any ideas on this? Thanks yet again. Dave.

I tried with windbg and that gave some information but I don't think it's much more than I got from Dr. Watson. I'm sorry but debugging isn't something that I'm at all experienced with! Anyway, I decided to try earlier versions of QuickTime to see if they had the same problems. I went back to 7.4.5 and that was exactly the same as 7.5. I then rolled back to 7.4.1, and everything worked perfectly! Apple must have done something between these two version to cause the problem with the masks. The double save window pop-up when saving from the browser plugin has gone away too! I think I'll leave it at that. I'm very pleased to have gone three versions on from the last one that was supposed to work with Windows 2000, and I doubt if the next two versions (7.4.5 and 7.5.0) give anything extra really worthwhile. Thanks for all your help, and keep on getting those non-2000 applications to work for us! You're doing a great job!

The respective path to MY Windows files is : D:\WINNT\SYSTEM32 , very similar to what you have. And it boots as designed to, whether using the original Windows 2000 Pro SP4 ntdetect and ntldr, or the replacement files from XP SP2. Please double check the contents of your C:\BOOT.INI file, esp. ARC paths in it. You should have a line similar to the following - but the rdisk(x) and partition(y) will vary according to your patitioning scheme, and you'll have WIN-NT instead of WINNT : multi(0)disk(0)rdisk(0)partition(4)\WINNT="Windows 2000 Professional" /fastdetect HTH [Edited] I realise your D: might be on a second physical drive, whereas my D: is a partition on the first physical IDE. I am quite sure however it shouldn't make a difference to the Windows NT bootloader, provided the correct BOOT.INI is present at the root of the partition from which BIOS boots the machine (which Microsoft, strangely, calls the "system partition". The partition which contains your WinNT files they call, also strangely, the "boot partition". IOW they have it in reverse... Need to keep this in mind when reading MS knowledge base articles) Thanks Ninho. I've tried with the files from Windows 2003 too, as per Ascii2's suggestion. Same result as before. In fact the ntdetect.com file is fine, it's the ntldr which is the problem. I even tried editing ntldr with a hex editor and changed a "c:\winnt" entry that I found to "d:win-nt". The system, wouldn't even start then, I just got "ntldr is corrupted, the system cannot start". Thank heavens for Windows 98 DOS boot disks! My boot ini is as follows - [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(2)\WIN-NT [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WIN-NT="Windows 2000 Professional SP4" /fastdetect C:\CMDCONS\BOOTSECT.DAT="Windows 2000 Recovery Console" /cmdcons C:\="Windows 98 Second Edition" Any clues there? My D: drive is a partition on the same physical drive as my C: drive, where Windows 98 sits. Is the fact that I have a dual boot system causing the problem I wonder.....? Cheers, Dave.

You need to replace BOTH ntldr AND ntdetect.com ! They belong to C:\ . Doing so does make the start of the boot sequence faster, and as a bonus, fixes bugs in the (optional, scrolling) display of loaded drivers. You assumed incorrectly. Also, having Win 2k setup as you described cannot be called non standard. It's not even unusual. HTH and please report back if my proposed "fix" works for you (if it doesn't I'm sure you'll be reporting anyway...) Well, I finally managed to get hold of ntldr and ntdetect.com from a Windows XP machine, so I could try this out again, this time replacing both files as suggested. Unfortunately, it still didn't work! On boot-up I immediately got the message - "Windows could not start because the following file is missing or corrupt \WIN-NT\SYSTEM32\CONFIG\SYSTEM" This is one of the registry files of course. I'm pretty sure that this is exactly what happened last time I tried this. Restoring the original ntldr and ntdetect.com files made everything come back to normal, so there obviously isn't anything wrong with my registry files. As I said before, I think the system just can't find the files because the path isn't what it's expecting. The path to the system files in the machine I took the files from would have been C:\WINNT\SYSTEM32. Mine is D:\WIN-NT\SYSTEM32, as I said before. I'd be interested in any further thoughts on this.

Thanks Ascii2. Managed to extract the kernel32.dll file OK once I knew that it wasn't actually a zip archive, despite the file extension! win2000, I put the debug kernel32.dll into the QuickTime folder, along with kernel2k.dll, and got some crash logs out of Dr. Watson and Norton Crashguard. How much use they are to you, I don't know. The Norton one certainly seems to be pretty basic. There is also a "user.dmp" crash dump file from Dr. Watson, but it's large (46MB) so I haven't included it. It is strange that the Norton2.txt log references "E:\Dump Folder\Video Masks\quicktim.exe". That folder is the folder where my masks are stored, NOT where the quicktim.exe (which is quicktimeplayer.exe in fact) program file is kept, so I don't know what's happening there......... See if the crash logs shed any light on what's happening. If not, I may try using earlier versions of QT7 and see if they display the same problem. Thanks, Dave.

Thanks again win2000, I'd like to try the debug as it may give you some clues as to what's happening. Unfortunately the file on your download link (http://blog.livedoor.jp/blackwingcat/arc/krnld028a.zip) seems to be only a 46kB file, which won't open!

Thanks again win2000. I was coming to the conclusion myself that the variable play speed option in WMP was an OS version based enhancement, and nothing to do with the player version. In fact something I read on the MS site implied that it is in fact there in WMP 9 if you use it under XP. That being the case, there isn't a lot of point in me having WMP 10 on my system. It looks a bit prettier than WMP 9, but if it doesn't actually give me any extra facilities when run under Windows 2000, there isn't any real advantage in having it. The mobile devices management facility didn't seem to work either. A new icon for it appeared in my Windows Control Panel, but it wouldn't actually do anything. I have no mobile devices anyway, so I won't miss it! I have uninstalled WMP 10 successfully, and gone back to 9. Can I just ask one more thing about Quicktime 7.5? It is working perfectly except for one thing. I don't know if you have the "pro" version. If you haven't you probably haven't run into this issue as the facility isn't there on the free version. There is a facility to apply a mask to movies in the "movie properties" dialogue in Quicktime 7. This has always worked fine for me, and I do in fact use it quite a lot. I now find with 7.5 on Windows 2000 that it doesn't work anymore. When I try to add a mask to a movie, the application always immediately crashes. Norton Crashguard reports "QuickTimePlayer caused fault #c0000005 in QTOControl.dll". Strangely, with movies which have been masked previously the mask can be changed without any crash. However if the mask is removed completely and the movie re-saved, it crashes if I try to add the mask again. Any ideas on this? QTOControl.dll seems to be what interfaces QT with the OS, so it could well be that the problem does indeed lie there. It is odd that everything seems to work perfectly except for that one function though. The only other slight anomaly I've noticed is that if you save a movie from the browser plug-in (again only possible with the "pro" version) when you save it puts up the save dialogue correctly, but on pressing "save" it saves the file but then pops up the save dialogue a second time! In fact it pops up the previous save folder that was used, not the last one, which is very odd. This isn't a severe problem obviously, but may be a clue as to what's happening elsewhere. Sorry to keep coming up with problems, I think you've done a great job getting these things to work on a supposedly incompatible OS in the first place, but if it's something easy to fix I thought you should know. Cheers, Dave.

Hi again win2000, Quicktime is still working fine. I have now tried to install Windows Media Player 10 using KDW, and thought I'd give you some feedback. You do have to install the XP kernel32.dll to the system32 folder for your installer to work, but as you say. once it's installed, you can use ez install to put the new kernel32.dll just in the WMP folder, restore the original Windows 2000 file to the system32 folder, and it continues working. I would like to keep your later kernel32.dll file in system32, and I do have your user32.dll, shell32.dll and advapi32.dll files there, but I have a problem with one of the Norton Utilities that I use if I do this. As I mentioned previously, the Norton Protected Recycle Bin service won't start with that version of kernel32.dll in the system32 folder. At startup, it puts up an error message which says - This error is presumably being caused by the new kernel32.dll file. Is there any way around this? Apart from this, Windows Media Player 10 is working under Windows 2000. Great job! I do have a couple of issues with that though, which I'd appreciate your feedback on. Firstly, I now have no video preview thumbnails in the Windows Explorer, which I did have when WMP 9 was installed. I quite like them and would like them back. Do you know why they have gone and how to restore them? The other thing that I'm puzzled at is that fact that there is no "Play Speed Settings" option under the "Enhancements " menu of my player. I've always been annoyed with WMP 9 that there is no frame by frame jog facility, and I thought that had been added in WMP 10. It mentions it in the help file, but it isn't actually there on my player. Any idea why? Thanks for all your work. I never thought that it would ever be possible to use later versions of QuickTime or WMP under Windows 2000, and I would always be stuck now with increasingly out of date versions. You proved me wrong! Cheers, Dave.

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.