Tommy

I personally cheat because I can't stand waiting for full formats. I have a copy of Windows XP SP3 on hand so I launch its setup and I do my partitioning and formatting, once it's done formatting, I pop the disk out, wait for the error and then reboot the computer. Then I put my Windows 2000 disk in and when it comes to partitioning and formatting, I just say leave as is with no changes.

Windows Live Messenger 2009 Update So, I was playing around with it again today and after digging a bit, stupid me found something and remembered....they DO have connection testers in the options menu. So, I decided to run them. Running a TCP test, it appears that I can actually connect to the server and data is able to be sent. So, it tells me I can use the messenger service. Well, no, not really. I put the password in and I get the same error saying that the service is temporarily out of commission. However, the connection troubleshooter caught my eye. Ooooh, let's click that! So, clicking on it and running the tests, which only seem to run part way BUT might be a huge breakthrough, it seems as though *for me anyway* that the default gateway test fails. It says that your gateway is offline. Now whether it's my service...or we're just missing a vital kernel extension, I don't know. However, it seems that may be the trouble we're having for getting it to actually connect to the service.

You can also find ATI/nVidia drivers on www.filehippo.com along with a lot of useful computer programs, along with their legacy builds.

Oh, I see. Well, I get these results when I profile programs in Dependency Walker, some aren't Vista+, some of them are programs designed for Windows XP as well, at least the functions in kernel32.dll that I listed pop up.

@blackwingcat It seems that we still have a few problems but I did notice a few functions that several programs I've tested out have in common...would it be possible to add these? kernel32.dll FlsAlloc FlsGetValue FLSSetValue FlsFree IsTNT shell32.dll SHCreateItemFromParsingName SHCreateQueryCancelAutoPlayMoniker SHGetFolderPathEx mpr.dll WNetRestoreConnectionA uxtheme.dll DrawThemeTextEx advapi32.dll EventRegister EventUnregister EventWrite RegGetValueW msvcrt.dll _get_terminate That's some of the more common ones I've noticed. I know it's a tall order but we might make a few breakthroughs if you're able and willing to add those to the kernel extension project.

I would like to say here, Windows Live Messenger 2009 now runs on Windows 2000, however it seems that it cannot connect to the servers. It cancels out with an 80010004 error. While this is no concern for me since I don't use it anymore, it's a step in the right direction for the kernel extension program. Edit: I may have found the reason why it doesn't connect. In the contacts folder which is in the Windows Live folder, wlcomm.exe complains that ordinal 327 cannot be located in dynamic link library OLEAUT32.dll. Whether anyone cares about this or not, I don't know. I would just like to think we could overcome this and be able to use one of the newer version of WLM on Windows 2000. @blackwingcat, if you are at all interested in looking into this issue, I will be more than happy to test it out for you.

Looks great!! Except one problem, I didn't experiment with anything else really but I tried the Windows 7 sidebar and Vista MS Paint and when it finds dependency issues, most of the text is in japanese rather than english. This is v20k2 Edit: It's in other places too. Like the explorer bar which I've attached. Edit 2: It seems I'm also having a few other issues, such as a few InstallShield installations not running, such involve NVIDIA display drivers (the NVIDIA Control Panel to be more precise which has an error code of 1152) And another attempt on VideoStudio x2 which gives me a 1158 error. Others seem to run and others do not. It seems random for whatever reason.

Well, like I said, I have v20c installed and it seems like there was no issues with that release. I can't say with any of them between that and v20g2 though since I didn't nab them.

The last version I had installed was v20c and I had just installed v20g2.

Office problem is fixed! However, it seems as though the start menu ignores special effects such as sliding up or fading in and out. Other menus and tooltips follow the rules but the start menu has for some reason stopped obeying your selection.

The latest kernel extension v20f seems to clash with Office. Outlook 2003 and Word 2007 refuse to run with it installed.

Has anyone figured out a solution to this problem or is this a lost cause? There's got to be something I'm missing if it'll work for blackwingcat, I'm willing to do more testing to get this to work if anyone else has more suggestions. I really would like to use this webcam with my main computer which has Win2k.

*Update* Okay, installed on Native Environment. First just the KB888111 and Update Rollup 1 with Service Pack 4, device couldn't load all the proper drivers (code 31). Chalked it up to DirectX since it was at it's native 7.0 version. So, I installed the February 2010 version of DirectX 9, back to square one. Code 10, the device cannot start. So, that's where I am right now.

Well, I'll download the link bwc gave me after work and I'll just wipe the hard drive once again and start over fresh. I have a Windows 2000 CD that has strictly SP4 slipstreamed on it and that's it so that way I can start out with only official updates and I'll report back with my findings after work. Thanks you guys for helping me so much, I really appreciate it!

Just a little clarification, is SP4SRPv1 the Update Rollup from Microsoft or is it something different?

Nope, the integrated webcam doesn't work either. The situation is actually the same for both webcams. I have absolutely no idea what I'm lacking to make these things work. But the problem always seems to lie in the imaging device (as shown in the screenshot a few posts ago).

I hope this works: http://ge.tt/4kOH2UK/v/0 That's the imaging driver that has problems.

I got the driver but it's too big to upload and I don't have any file sharing accounts anywhere, how would you like me to get this to you?

I see no problems at all. It didn't give me any errors about it missing anything. I even checked everything in the driver details list and nothing seems to show up outside the mpr.dll and dbghelp.dll that I often see in other applications.

I don't think I did, but I will do that. However, Tomasz said that KB888111 was already in UR2, but I will install it again anyway. Edit: Tried installing it, no difference. It didn't seem to install anything so it must be installed already. How would I check on dependencies for the driver?

Nope, nothing at all. I'm attaching my device manager to here, maybe you'll get a better idea of what I'm talking about. When I launch the Logitech software, it keeps saying there's no camera detected. I'm using version 1.10.1113.0 software as described here: http://blog.livedoor.jp/blackwingcat/archives/1073845.html The high definition audio device not installed has nothing to do with the webcam, I'm really not sure what it deals with but I know there's a sound driver for the webcam installed.

Okay, here's what I did. I clean installed Windows 2000 completely, so now I'm down to all updates, USP5.1, UR2, and BWC Kernel 17f, I still get the same exact results as before. The BSoD occurs when I try recording audio via sound recorder. I can't even get the imaging driver to start. Under imaging devices it shows up but with a yellow circle and a black ! in it. It shows up as Code 10, device cannot start.

Oh, I see. I figured this was slightly different than the actual kernel extension. I will try uninstalling UURollup and then retest and see what happens.

I hope this helps D: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: 00000004, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 8086e5d7, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: nt FAULTING_MODULE: 80800000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ff7c978 BUGCHECK_STR: 0xC5_2 CURRENT_IRQL: 2 FAULTING_IP: nt+6e5d7 8086e5d7 ?? ??? CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from 00000000 to 8086b1e8 STACK_TEXT: STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt+6e5d7 8086e5d7 ?? ??? SYMBOL_NAME: nt+6e5d7 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

I will try a newer driver later after work. I did not install Windows Media Player either. But I made sure that I followed the steps we talked about to fix it and it made no difference. I should mention I have UURollup 10 installed as well.