Nvidia Windows 2000 Xp 32bit Driver Library Installation Disk 1

Load DriverA media driver your computer needs is missing. This could be a DVD, USB, or Hard disk driver. If you have a CD, DVD, or USB flash drive with the driver on it, please insert it now. Note: If the installation media for Windows in the DVD drive or on a USB drive, you can safely remove it for this step.

Nvidia Windows 2000 Xp 32bit Driver Library Installation Disk 1

Load DriverA required CD/DVD drive device driver is missing. If you have a driver floppy disk, CD, DVD, or USB flash drive, please insert it now.Note: If the Windows installation media is in the CD/DVD drive, you can safely remove it for this step

Visit VOGONS Vintage Driver Library for Mesa3D, SwiftShader drivers.Here is an older wrappers, renderers which are tested: Realtech VR DXGL Wrapper, AltOpenGL, TechLand Soft OpenGL, mesaFX OpenGL, SciTech Software GLDirect.Tested video cards/chipsetsVBE 3.00 INTERNAL Intel 6/7/8 Series Chipset GraphicsVBE 3.00 INTERNAL Intel G31/G33/G41/G43/G45 GraphicsVBE 3.00 INTERNAL Intel G963/G965 GraphicsVBE 3.00 INTERNAL Intel 945G GraphicsVBE 3.00 INTERNAL Intel 915G GraphicsVBE 3.00 INTERNAL Intel 910G GraphicsVBE 3.00 INTERNAL Intel 865G GraphicsVBE 3.00 INTERNAL Intel 852G GraphicsVBE 3.00 INTERNAL Intel 845G GraphicsVBE 3.00 INTERNAL Intel 815G GraphicsVBE 3.00 INTERNAL Intel 810 GraphicsVBE 2.00 AGP 8Mb ATI Rage 3D Pro AGP 2x (BGA Package)VBE 2.00 AGP 8Mb ATI Rage P/M Mobility AGP 2xVBE 2.00 AGP 32Mb ATI Rage128 PF/Pro AGP 4x (TMDS)VBE 2.00 AGP 64Mb ATI Radeon 9000 Series (RV250)VBE 2.00 INTERNAL ATI Radeon Xpress 200M SeriesVBE 3.00 16Mb? ATI Radeon X1650 Series (RV530 LE)VBE 3.00 16Mb? ATI Radeon X1950 GT [RV570]VBE 3.00 AGP 16Mb 3Dfx Interactive Voodoo3 2000VBE 3.00 PCI 4Mb nVidia RIVA 128 2D/3D Gui AcceleratorVBE 3.00 AGP 4Mb nVidia RIVA 128 2D/3D Gui AcceleratorVBE 3.00 AGP 16Mb nVidia RIVA TNT GUI+3D Accelerator [NV4]VBE 3.00 AGP 16Mb nVidia RIVA TNT2 Model 64 [NVM64]VBE 3.00 AGP 32Mb nVidia GeForce2 MX/MX400 [NV11]VBE 3.00 AGP 64Mb nVidia GeForce2 GTS/PRO [NV15]VBE 3.00 AGP 64Mb nVidia Geforce3 Ti 200 [NV20]VBE 3.00 AGP 128Mb nVidia GeForce FX 5200 [NV34.3]VBE 3.00 INTERNAL nVidia GeForce 6100 nForce 430VBE 3.00 nVidia GeForce 7600GSVBE 2.00 PCI 4Mb Matrox MGA-2164W Millenium II PCIVBE 3.00 AGP 16Mb Matrox MGA-G450 AGPVBE 3.00 AGP 8Mb Matrox MGA-G200 AGPVBE 2.00 AGP 4Mb Matrox MGA-G100 AGPVBE 2.00 PCI 4Mb TSENG LABS Inc ET6000VBE 1.32 INTERNAL 1Mb TSENG LABS Inc ET4000VBE 2.00 AGP 4Mb S3 Inc 86C368 Trio3D/2XVBE 2.00 PCI 2Mb S3 Inc 86C375 ViRGE/DXVBE 2.00 VLB 2Mb S3 Inc Vision964VBE 2.00 INTERNAL 2Mb Cirrus Logic CL-GD546VBE 1.02 INTERNAL 1Mb Cirrus Logic CL-GD5428VBE 1.02 INTERNAL 512Kb Cirrus Logic CL-GD5424VBE 1.02 VLB 1Mb Cirrus Logic CL-GD5428VBE 1.02 PCI 1/2Mb Cirrus Logic CL-GD5446 PCIVBE 1.02 PCI 2Mb Cirrus Logic CL-GD546x PCIVBE 2.00 INTERNAL Trident CyberBlade i7VBE 1.02 ISA 1Mb Trident 8900VBE 1.02 ISA 512Kb Trident 9000i [True Color DAC]VBE 1.02 ISA 256Kb Realtek 3106 [RTG3106]no VBE ISA 256KB Cirrus Logic CL-GD5401 - Acumos VGA (AVGA1)VBE 2.00 PCI 8Mb? VirtualBox VBE Adapter (Innotek VirtualBox)VBE 2.00 PCI 16Mb VMware SVGA II (VMware)VBE 2.00 PCI 4Mb Cirrus Logic CL-GD5446 PCI (QEMU)VBE 2.00 PCI 4Mb IBM Plex86/Bochs VBE Adapter (QEMU/Bochs) VBE 2.00 PCI ?Mb IBM Plex86/Bochs VBE Adapter [vmware] (QEMU/Bochs) no VBE ISA 256KB Elpin VGABIOS (Bochs)Driver troubleshootingWhen you have problems with VBEMP, there are two basics scenarios:Computer starts, but driver is not working properly.Computer not starts, i.e. crashes, having BSOD or "hang".Before debugging try these actions, provided below:Physically remove memory chips or uses /MAXMEM boot.ini's switch to do it in this manner (if you have 1024 Mb RAM): 512 -> 256 -> 128 -> 64 -> 32 -> 16 -> 8.Upgrade motherboard's BIOS to the latest version.Clear CMOS settings to default or safe.Decrease AGP Aperture in BIOS as it is unused by VBEMP.Temporarily remove any external controllers as: usb, sound, hdd, lan or others.Try a videocard with another bus: AGP, PCIe, PCI, onboard.To start debugging process you MUST request a LOGGED-version (for method 1) or a DEBUG-version (for methods 2,3) of driver from me by e-mail. For methods 2,3 you MUST READ this article WinDbg basicsHOWTO for QA engineers to understand which debug method is suitable in your case. Here are the solutions in brief:Method #1 (using logged version): Install logged version. When it runs, logging is made to %SystemRoot% location (which is usually "C:\WINDOWS" or "C:\WINNT") to logfile vbemp.log. Please send me this log after you system is loaded or crashed.Method #2 (using DbgPrint logger): Download KdPrint/DbgPrint logger (the 1st one, "archive with all necessary files"). For NT 3.5x debugging use THIS [?],[?],[?] version. It also works with later Windows NT versions.Extract it to somewhere (for example, in C:\DbgDump)Start cmd.exe (via Start -> Run, simply enter therecmd.exe and click Run)In opened window enter:C: [Enter]cd C:\DbgDump [Enter]DbgPrintLog -wd C:\ --drv:inst 1 --svc:inst A --drv:opt DoNotPassMessagesDown 1 --drv:opt StopOnBufferOverflow 0 BootVbe.log [Enter]Reboot. Make sure that logfile is made. C:\BootVbe.log must exist.Install VBEMP driver.Reboot. After that, you get a logfile from my driver C:\BootVbe.log. Send me it by e-mail.Now it is time to disable logger: run cmd.exe (see above)In opened window enter:C: [Enter]cd C:\DbgDump [Enter]net stop DbgPrintLog.exe [Enter]DbgPrintLog --drv U --svc U [Enter]Method #3 (using WinDbg/i386KD): You may use Windows 32bit x86 kernel debugger WinDbg/i386KD to trace debug logging information from the driver via serial port.Connect two PC's using nullmodem serial cable with this pinout:MSKB: How to set up a remote debug session using a null modem cable (Q151981)9-Pin NULL Modem CablingRemote hostserial port connector Host systemserial port connectorSignal3 2 Transmit Data2 3 Receive Data7 8 Request to Send8 7 Clear to Send6, 1 4 Data Set Ready and Carrier Detect5 5 Signal Ground4 6, 1 Data Terminal Ready25-Pin NULL Modem Cabling2 3 Transmit Data3 2 Receive Data4 5 Request to Send5 4 Clear to Send6 20 Data Set Ready and Carrier Detect7 7 Signal Ground20 6 Data Terminal ReadyFor Windows NT3/NT4/W2K/XP/2003:On target PC - edit boot.ini file, placed in the root dir of your hard drive; before:[boot loader]timeout=30multi(0)disk(0)rdisk(0)partition(2)\WINNT[operating systems]multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Version 4.00"multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Version 4.00 [VGA mode]" /basevideo /sosAfter:[boot loader]timeout=30multi(0)disk(0)rdisk(0)partition(2)\WINNT[operating systems]multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Version 4.00"multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Version 4.00 [VGA mode]" /basevideo /sosmulti(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Version 4.00 DBG" /debug /baudrate:19200 /debugport:COM2When starting target PC you must select in menu "Windows NT Version 4.00 DBG" line for debugmode activation.For Windows NT3/NT4/W2K/XP/2003 in first boot stage and also for WindowsPE:On target PC - edit txtsetup.sif file, placed in the /I386 or /MININT dir of your boot drive; before:[Version]signature="$Windows NT$"ClassGUID=00000000-0000-0000-0000-000000000000 . . . . . . . . . . . .OsLoadOptions ="/fastdetect /minint /noguiboot" . . . . . .After:[Version]signature="$Windows NT$"ClassGUID=00000000-0000-0000-0000-000000000000 . . . . . . . . . . . .OsLoadOptions ="/fastdetect /minint /noguiboot /debug /baudrate:19200 /debugport:COM2" . . . . . .On host PC - install Microsoft x86 32-bit Debugging Tools ( ).After that create cmd-file for starting i386kd.exe and place it in Debugging Tools directory:@del *.log@cls@rem Specify which com port to use. (Default = com1)@set _NT_DEBUG_PORT=com2@rem Specify the baud rate used by debugging serial port. (Default = 19200)@set _NT_DEBUG_BAUD_RATE=19200@rem If specified, all output will be written to this file from offset 0.@set _NT_DEBUG_LOG_FILE_OPEN=vbe.log@i386kd.exe -v -failincFirstly, connect two PC's via serial cable.Secondly, start host PC and execute cmd-file.Then start target PC. It will be started in debugmode.If target PC hangs, break i386kd on debugger PC ([Ctrl]+[B],[Enter]) and send vbe.log to me.After you produce logs from driver you can give me additional information about your system and video adapter. This step is optional!!! Without driver logs this information is meaningless for me!!!Collect VESA BIOS and system information :Download NEW 2in1 INFOVBE.EXE ([?],[?],[?]) tool. This archive also contains 1.44 Mb bootable floppy image with this tool for users who don't have DOS or Windows9x already installed. You must run it under pure MS-DOS (Real Mode) like: INFOVBE.EXE > vbe.txtDownload Craig Hart's PCI32, pci104vka tool(s) and PCI devices list (place them in one directory overwriting existing version of pcidevs.txt). You must run it under Windows NT/2K/XP/2003 like: PCI32.EXE -R -D > devpci.txtpci_w.exe -R -D -P -M -5 > devpci.htm Please send me vbe.txt, devpci.txt, devpci.htm in compressed view (rar, zip, 7z...) by e-mail.For ISA/MCA/VLB card owners: There are new tools - lfb_det.exe/lfb.exe, which can automatically detect linear frame buffer address of your card in system address space. They are distrubuted only by request via e-mail. Read pp.3 ("Collect system information"), make logs and I will send you these tools.VBE FAQ: VESA BIOS Extensions standard deviation listCards (chips) affectedDescriptionIntel 845G, 855G, 865G, 915G and laterPRB: Cannot set native resolutions i.e. 1024x600, 800x480, 1280x800, mostly on notebooks with Intel integrated graphics.DETAILS: In Video BIOS - mode tables these non-standard modes are absent or filtered. When you try to ask BIOS to set it, BIOS returns an error.FIX: Update your BIOS with latest version or patch it. In DOS/Windows9x it is possible to use software Intel TSR VBIOS VESA-driver.Intel 845G, 855G, 865G, 915G and laterPRB: Cannot set resolution higher than 800x600x8bits and 640x480x16bits.DETAILS: In Video BIOS frame buffer size hardwired to 832 Kbytes, which is not enough even for 1024x768x16bit = 1024*768*2 = 1572864, 1572864 > 832K.FIX: Update your BIOS with latest version or patch it. In DOS/Windows9x it is possible to use software Intel TSR VBIOS VESA-driver.Intel 810E, 815E seriesPRB: Cannot use linear frame buffer, but card identifies itself as VBE 3.0 compatible.DETAILS: In Video BIOS linear frame buffer support is absent, but card itself supports linear frame buffer.FIX: None known.ATI Radeon Xkkkk series (starting with X700)PRB: Cannot use custom screen refresh rates, but card identifies itself as VBE 3.0 compatible.DETAILS: In Video BIOS screen refresh rates switching code is absent. When you try to ask BIOS to set it, BIOS immediately returns VBE error 0x34F.FIX: None known.nVidia GeForce 5xxx/6xxx/7xxx (and newer ones)PRB: Cannot use custom screen refresh rates, but card identifies itself as VBE 3.0 compatible.DETAILS: In Video BIOS screen refresh rates switching code is changed. When you try to ask BIOS to set it, BIOS always sets default refresh (60 Hz).FIX: None known.Intel 7/8 Seies Chipset Graphics (and newer ones)PRB: Cannot use custom screen refresh rates, but card identifies itself as VBE 3.0 compatible.DETAILS: In Video BIOS screen refresh rates switching code is changed. When you try to ask BIOS to set it, BIOS always sets default refresh (60 Hz).FIX: None known.nVidia GeForce 5xxx/6xxx/7xxx (and newer ones)PRB: Cannot set any resolution higher than 800x600.DETAILS: In Video BIOS - mode tables 1024x768 modes and higher are absent or filtered. When you try to ask BIOS to set it, BIOS returns an error.FIX: Update your BIOS with latest version or patch it.VESA 1.x cardsPRB: When accessing fullscreen textmode, computer "hangs".DETAILS: In Video BIOS mode-set routines are badly written for calling them in 32 bit protected mode.FIX: None known. In DOS/Windows9x it is possible to use software VESA-driver.Different VESA cardsPRB: When calling VBE functions, highword bits of EAX register and may be others (i.e. 0x????0000) may contain garbage.DETAILS: In Video BIOS VESA routines are badly written for calling them using 32 bit registers.FIX: Filter highword bits of EAX.Matrox, Trident, TsengLabs cardsPRB: When calling VBE functions, 16-bit R5G5B5 and R5B6G5 modes both reported as 16-bit. In some cases it confuses VESA programs - if I choose 16-bpp mode, which color model (555 or 565) will be used?DETAILS: In Video BIOS VESA routines are incorrectly written. Microsoft FRAMEBUF.DLL driver confuses and skips 15-bpp modes if they are reported as 15-bpp. If both 555 and 565 modes are reported as 16-bpp, FRAMEBUF.DLL uses first scanned one.FIX: When choosing such modes check both bpp value (15 or 16) and bits values (555 or 565). I've made a modified version of FRAMEVBE.DLL.Project historyJUL 12, 2005: initial "Manual" version is made.FEB 20, 2006: first public released "Universal" version of vbemp.sys (VbempXP/VbempNT5/VbempNT4/VbempNT3). Includes both VBE 2.0 code and experimental VBE 1.02 code. There are some problems with ATI Technologies cards.NOV 04, 2006: 320x200x8bit "tricky" driver (Vga13H) for old VBE 1.02 cards released due to some incompatibilities with such cards in main version of driver - TEMPORARY solution for implementing LFB-emulation.NOV 18, 2006: new BETA of driver. All code related to VBE 1.02 and bank switching removed. do not try to use this driver on VBE 1.02 cards.NOV 28, 2006: again, new BETA of driver. VBE 1.02 ISA-based cards now works only in 320x200x8bit mode. Begin driver adaptation to PCI video cards based on VBE 1.02 (1995-1998 yy.).DEC 01, 2006: previous "Universal" version is revised & replaced in downloads.DEC 02, 2006: also renew "Manual" version.DEC 11, 2006: last "Universal" version is now 2in1: MTRR USWC and normal. MTRR version is somewhat faster. PnP is working better now.DEC 23, 2006: minor site/page re-design.DEC 26, 2006: current driver quickly adapted to Windows XP/2003 from scratch. Some screenshots of "Vbemp in work" added.DEC 29, 2006: site cleanup, previously released Windows XP/2003 driver version revised - removed nonworking functions.JAN 07, 2007: beta version of driver for Windows XP/2003 released with VESA DDC support and refresh rates switching (43-120Hz).JAN 10, 2007: 320x200x8bit "tricky" driver (Vga13H) updated with recent changes in PnP, Monitor DDC and VBE power management features.FEB 13, 2007: released last betas of VBEMP for NT3/NT4/W2K with APM and VBE 3.0 support in one archive of January 13th.MAR 24, 2007: released last betas of VBEMP for NT3/NT4/W2K with APM and VBE 3.0 support in one archive of February 19-20th. Site re-design.MAR 31, 2007: due to some stability problems in VBE 3.0 code two versions of VBEMP (except for XP/2003 version) beta released now: VBE30 and VBE20 (VBE20 version does not support refresh rate switching).APR 18, 2007: due to user convenience BUILDVBE tool merged with INFOVBE tool.APR 19-22, 2007: bugfixed beta VBEMP re-released. XP/2003 version is not affected.APR 25, 2007: released two NEW betas: STDVID (4 EGA/VGA 16-color modes 0Dh/0Eh/10h/12h) and VGAMONO (emulate True Color on 640x480x2 - 11h).APR 27, 2007: VBE30 and IOCTL calls are now more accurate.MAY 04, 2007: detailed INFOVBE and NEW VBE3TEST tools are released.MAY 17, 2007: new VBEMP with pre-alpha ISA/MCA/VLB LFB cards support released.JUN 03, 2007: new VBEMP with legacy-mode support released.JUN 17, 2007: VBEMP with minor fixes and NT 3.1/NT 3.5 support is out.JUN 25, 2007: minor site changes.JUL 15, 2007: VBEMP control panel extension is made.JUL 21, 2007: INFOVBE tool updated.JUL 22, 2007: recent VBEMP with mode filtering, monitor detection enhancements and parsing edid in legacy mode.AUG 17, 2007: "Manual" version release refreshed with latest VBEMP changes and some minor fixes in installation.AUG 31, 2007: minor site changes.OCT 6-28, 2007: small fixes in VBEMP, VBEMPCpl and new FRAMEVBE library.MAR 05, 2008: minor site changes and new FRAMEVBE library is out.APR 19, 2008: long awaited new version of VBEMP is out.APR 26, 2008: small fixes in VBEMP and site redesigned.APR 29, 2008: INFOVBE tool updated.OCT 05, 2008: new VBEMP beta.NOV 16, 2008: another VBEMP beta, mostly VESA 3.0 GTF related.NOV 30, 2008: FRAMEVBE library with NT 3.5x support released.DEC 19, 2008: new VBEMP control panel extension released.JAN 03, 2009: VGA13h back to life, replaces STDVID.JAN 08, 2009: CL54xx driver bugfix release.JAN 14, 2009: INFOVBE, VBEMP releases with minor enhancements.JUN 05, 2010: new FRAMEBUF, FRAMEVBE beta.JUN 09, 2010: new VBEMP beta.JAN 01, 2015: long awaited :) new VBEMP and CL54xxMP betas.DEC 01, 2019: long awaited :) new VBEMP and CL54xxMP betas.Changelog[!] Important[+] New[-] Fixed error[*] Changes[?] Comments2005.05.07[!] initial "Manual" version. later revised2005.07.12[!] pre-release "Universal" version. later revised2006.02.20[!] initial "Universal" version.2006.11.09[*] no vbe 3.0, i.e. no refresh rates - COMMENTED[*] no child devices (w2k+ all) - COMMENTED[!] vbe oem strings & modelist broken on some video cards[?] svga memory size=0 broken ? in vbe 1.02 (use split videomodeptr?)[!] vbe 1.x modes > 64 kb does not work[+] only 320x200x8bit in vbe 1.02[?] no fullscreen text mode in vbe 1.02 cards, why? on 80486sx33/16mb - works...2006.11.11[!] try isa lfb at 0x0F00000 ? suckz![!] _NT_DEBUGGING_EXTENSION_PATH ?...Loaded dbghelp extension DLLThe call to LoadLibrary(ext) failed, Win32 error 127 "The specified procedure could not be found."Please check your debugger configuration and/or network access.... what is it? = use latest? version of WinDbg2006.11.18[*] Map all memory or a part of it, like in 640x480x4 - map needed part only[*] disable Uncached Speculative Write Combining (USWC) feature[+] use low res modes? - YES[+] crop biosregs.eax to 0x0000ffff ? - YES[!] nt3 is about to ioctl_share_memory/unshare (640x480x4) for DCI - NO[*] XMill/YMill from ROS 0.3.0 - YES[*] temp. removed all vbe 1.02 code!!!2006.11.19[!] remove TrampolineMemory2 & man.added +0x200 - ?[!] on Radeon 9000 vbe4 and vbe3 not working, "hangs" PC2006.11.28[?] got a rare VBE 1.02 PCI CL5446 SVGA... 1996yr -