Dave-H

I posted a guide on page 4 of this thread which I thought would be helpful. Have a look and see if it does help explain how to use KDLLINST. Especially "EZ KD Registry" must be checked or you will risk BSODs on start-up. Note that the "Japanese character" in the paths mentioned seems to have been fixed in the latest version.

I'm a bit puzzled why your System Properties says "Microsoft Windows NT" and not "Windows 2000" as mine does. All the other details are the same, with the addition of the "Windows NT-Update: 14.10.2008" bit. I'm not sure what "Windows NT 5.0 EUR Edition" actually is. All I know is that KDW was specifically targeted at Windows 2000 SP4, and if your OS is flagged as something different that may well be why things are not working as they should. Sorry not to be of more help here.

I don't know about MSN Messenger, but for WMP10 I think you must use win2000's special installer. The normal one won't work. You can get it here - http://blog.livedoor.jp/blackwingcat/archives/37690.html Worked for me!

Hi win2000. Can I get any answer as to whether there's any hope of my AVS Video Tools working with your kernel32.dll installed? I'd like to know as it affects how I want to configure my machine from now on. Thanks for all you do.

There is an option to set the number of days for transfers to be kept in the list, copy and paste this into the address bar: opera:config#TransferWindow|KeepEntriesDays The default is 7 days, but I've never been convinced that it makes any difference! Did you try that skin?

If you want the look of Opera 9.2x back in 9.5/6 the shin here should do the trick - http://my.opera.com/community/customize/skins/info/?id=8248 It's not the real 9.2 native skin, but one made by someone to replicate it. Gets rid of those black icons by all accounts though! I love Opera because it's the most user customisable browser out there, you can get it to look exactly the way you want it to if you know how. The thing with items disappearing from the transfers window is very long standing. They do disappear by design incidentally if the item concerned is deleted or moved from the folder it was downloaded to.

Have you tried just using different skins?

I seem to remember that it looked like that when I installed it too. (I've uninstalled it again now and gone back to WMP9 as WMP10 didn't give me any advantage that I could use.) I just assumed that was the default skin for WMP10. Have you tried the different skins available to see if the look you expected is in fact available?

Thanks yet again win2000! I decided to go for the latest version of Real Player 11 rather than the one you suggested, as it seems to be a beta. Once I realised I had to use fcwin2k (in a mode I'd not used before!) it all worked fine. You are indeed a genius! :thumbup Now please yet again is there any hope of getting AVS Video Tools to work with your kernel32.dll installed...........? If that were possible my happiness would be complete!

Have you got the "EZ KD Registry" option checked in the KDW file installer window? I found my system had a stop error like that if the system file registry entries weren't correct. If it's not checked, check it and try the file replacement again.

Hi win2000. Thanks for the quick reply. FileHippo has all of the previous versions of Real Player 11 for download http://www.filehippo.com/download_realplayer/tech/ Unfortunately none of them work for me, even the very earliest beta versions. The file you mention, rnsetup0.exe, does not exist in the temp folder with any of them. Can you tell me which version you did get to work and where you got it from? Thanks, Dave.

Thanks very much for all that! I have never used NTFS partitions, but the general principles of what you did are similar to what I want to do. I am now pretty convinced that the reason why the later Windows start-up files will not work for me is fundamentally because my Windows 2000 installation is not on the C: drive. I certainly don't want the drive letter allocations to be different on my two operating systems. From what several people have said, Windows 98 will not work unless it is on the C: drive, so it looks as if there's nothing I can do to resolve this. I will just have to put up with the "as designed" Windows 2000 boot speed. I would be very interested to hear from anyone who has got this to work on a dual boot system, and what the configuration of that system actually is. Glad that at least I've flagged this option to people generally, as several people have reported that their boot times have significantly improved by using later files, whatever the theory may say! I did get my initial startup back to as it was before BTW, by repairing the MBR using the Repair Console. It didn't make any difference on the first reboot, but after that it was back to as it was before. Thanks all. Cheers, Dave.

There you are - NTLDR NTDETECT.COM Right click and "Save Target As" please! Let us know what difference these files make. They are from Windows Server 2003.

Hi win2000, How do you actually install Real Player 11? I have all your modified system files installed. When I run the standalone installer I just get a message after it unpacks which says that I need at least Windows XP. I have looked in the WINNT\Temp folder before aborting the installer and there don't seem to be any .msi files to modify. The online installer just says that my computer doesn't meet the system requirements and aborts the install. So how do you actually do it? Thanks, Dave.

I had this same problem, and it was mainly due to too much stuff in my autoexec.bat. I went to this "bare bones" version, and it worked - @ECHO OFF PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\WINDOWS\SYSTEM MODE CON CODEPAGE PREPARE=((850) C:\WINDOWS\COMMAND\EGA.CPI) MODE CON CODEPAGE SELECT=850 KEYB UK,,C:\WINDOWS\COMMAND\KEYBOARD.SYS This is set for a UK English configuration of course. Also I had to REM out a line in my config.sys to get Auto-patcher to run, as indicated - SHELL=C:\WINDOWS\COMMAND.COM /E:768 /P REM ** REM OUT THE PREVIOUS LINE WHEN USING AUTO-PATCHER ** DEVICE=C:\WINDOWS\COMMAND\ANSI.SYS COUNTRY=044,850,C:\WINDOWS\COMMAND\COUNTRY.SYS DOS=HIGH,UMB,AUTO Give that a try. Good luck!

It seems protection from cheat by DLL injection as same as nProtect technology, cause of AVS is shareware. AVS isn't actually shareware, it is a paid-for commercial program. I do have a licence BTW! Is there likely to be any way around this? It won't work using the EzInstall trick that I used to get my Norton Utilities working BTW, I've already tried. I see, I wonder that irv files can be played as I play the rm and ram files on WMP 10. I think only that If there is any sample irv file , I try it on WMP10. I'm pretty sure that they won't play on any version of WMP. If VLC Media Player can't play them, I'd be very surprised if WMP 10 or 11 can.

Yes, I realise of course that I can't use NTFS if I want Windows 98 to read the drives. Really good to know that you have had systems with Windows 2000 on the C: drive and Windows 98 on the D: drive though. Thanks very much!

Sorry I don't have any to hand, but they are becoming more common. They will play in Real Player 11, but as far as I know in nothing else. Any chance of sorting out the problem with AVS Video Tools? http://www.avsmedia.com/videotools/download.aspx

Thanks win2000, I didn't realise that Real Player 11 was one of the applications that does work on Windows 2000 if KDW is installed. That's great news. Unfortunately if it needs your kernel32.dll installed, I can't do it because I still have the problem that my AVS Video Converter won't work anymore if your kernel32.dll is installed. If you can find a fix for that it would be great. It's strange because AVS Video Tools is a Windows 2000 and XP compatible program, so I don't understand why it doesn't like a modifed kernel32.dll file with XP entry points added, because surely they are there in the "proper" XP dll! Very strange.

Good news!

Yes indeed, sorry of course you were quite right! The order that my operating systems were installed in is the "correct" one. I just wonder if it is actually possible for a dual boot system to work correctly if Windows 98 is on drive D: and Windows 2000 on drive C:. There is a MS KB acticle which actually goes into this - http://support.microsoft.com/kb/283433

Glad you're up and running again win2000. Don't burn out this machine! I hope you might be able to now find out what the problem is that AVS Video Tools has with your modified kernel32.dll file. Also, could I put in yet another request (I realise that you've been getting loads!) I keep running into .ivr video files. These are coded using a Real Media codec, and can only be played using Real Player 11 or later. Of course on Windows 2000 (and Windows 98) you can only use Real Player 10.5, which recognises ivr files but won't play them. I haven't been able to find any other player which will handle them, even the latest VLC Media Player doesn't want to know. Is there any possibility of making Real Player 11 work on Windows 2000? Cheers, Dave.

Thanks again James. Yes, Ranish is a DOS program. If you run it in Windows 2000 it just prompts you to copy it to a floppy and boot from that. I just booted into "command prompt only" DOS mode (which I can do as I have Windows 98 installed of course) and used it from there. With regard to "installing the latest OS last" of course that wasn't the case with my system, which was Windows 98 only for years and then had Windows 2000 added. "the xt guy" seemed to be saying that Windows 98 has to be first as that has to go on the C: drive and won't work on the D: drive. This implies that it isn't possible to add Windows 98 to a Windows 2000 system, as two operating systems can't share the same partition and therefore 98 can't go on the C: drive as 2000 is already there! I'm getting really confused........ Now I just wish I knew why the first stage of Windows 2000 startup is taking even longer than it did before.

It's gone very quiet................. Does anyone actually know any reason why I shouldn't swap my operating systems over so Windows 2000 is on C: and Windows 98 is on D: ? I might actually be able to use the later NTDETECT.COM and NTLDR files then. More importantly, since I did all my messing about, although apparently everything is back to as it was before, Windows 2000 is now taking even longer to start up than it did before! Quite the reverse of what I was trying to do in the first place of course! Mainly it's now spending ages crawling along the very first "Starting Windows" progress bar, far longer than it used to, even though the NTDETECT.COM and NTDLR files are back to the ones that they always were. Anyone any idea why this might be?

Are you saying therefore that you can't add Windows 98 to a machine that already has Windows 2000 on it? In that case Windows 2000 would already be on the C: drive so Windows 98 would have to go elsewhere. My Windows 2000 Resource Kit Book doesn't seem to say that there would be any intrinsic problem with that, only that you might have to use the Windows 2000 Repair Console after installing Windows 98 to repair the Master Boot Record, as it would have been over-written by Windows 98 Setup.