- You are running Windows 95B OSR 2.0 or 2.1 4.00.950 B. Or type this command at any DOS prompt: VER. And press Enter. It should return a message like this (example): Windows 95. Windows 4.00.1111 This means your OS is Windows 95B OSR 2.0 or 2.1 4.00.950 B or Windows 95C OSR 2.5 4.00.950 C, which run both on top of MS-DOS version 7.10.
- Windows 95 ISO images are available through our downloads listed below in each release. Have something to share about Windows 95? Comments on any WinWorld articles are welcome over on WinBoards, WinWorld's discussion forum. Chicago; 95 Demo; RTM; OSR 1; Patches; OSR 2; OSR 2.5; Windows 95 OSR2 ('B' version) added support for FAT32.
Download Windows 95 OSR 2.5.If you have a Windows 98 ISO and it won't boot, then you will have to download a Windows 98 Boot Disk from the link below!
These instructions assume a CD-ROM on the installation machine.
But I don't HAVE a CD-ROM
Get one. I won't help you if you don't have a CD-ROM on a Windows95 machine. CD-ROMs are very cheap now, and my time is not.Step 1: Start from a clean computer.
Don't do upgrades. After a few experiences, I won't waste my timetrying to fix a Windows Upgrade. It works sometimes. Perhapseven often. However, nowhere near enough to be worth subjecting yourselfto the problems. And, even if it works initially, all the garbagefrom older versions of Windows will give you nightmares some day.But I only have the UPGRADE version of Windows 9x!!
Yes. I'm sorry. Microsoft, in their infinite monop..er..wisdomhas decided to only sell Windows 95 as an Upgrade to consumers. You would think they had learned this doesn't work properly with Windows95. The good news is the Upgrade versions only ask you to PROVEthat you have the old version, you don't have to INSTALL the old versionof the software. Windows 95 Upgrade will ask you to insert Disk 1. I understand the Windows 98 upgrade does something else, not sure what,but I understand it is more unpleasant. Oh, well.Now, inspite of the official ban against selling full OEM versions toend users, many, many small computer stores will HAPPILY sell you a copyof Windows 9x OEM. I will not name any names. But if you seea small hole-in-the-wall computer store, odds are they will sell it toyou. Forget the big places, though.
Another reason to avoid the Windows 95 upgrade: It is only availablein the origional release. This means if you want anything cool fromRelease 2 (OSR2 as some people call it, Release B as others call it), youHAVE to go through less than legitimate channels. There is no wayto get Win95r2 legimiately other than to buy a computer with it (and thenyou can only use it on that one computer...)
Update: It appears it *is* possible to buy a 'legitmate' copyof Windows 98 full release, box and all. 'Bout time.
The computer should have NO WINDOWS directory on it. IF you mighthave some data lost in an upgrade, you could Rename the WINDOWSdirectory to some other name, if you so desire.
But, I don't WANT to wipe my system out!
You like what you have? Then don't upgrade! Keep it! Or, don't come whining to me about the results.Step 2: Boot machine from floppy, prepare hard disk, get CD-ROM running
Windows 95 r2 and Windows 98 include a boot floppy.Windows 98: The Windows 98 boot floppy includes several popularCD-ROM drivers, including some SCSI controllers and a driver which appearsto work with most IDE CD-ROMs.
Update: It is possible to boot off the Windows 98 CD-ROM. To my surprise, the boot disk and the boot image on the CD-ROM are different. Go figure. However, either source works pretty well.
Windows 95r2: The boot disk doesn't include any CD-ROMdrivers...you will have to make a copy of this disk (DISKCOPY) on anothercomputer, and provide your own CD-ROM driver for your own CD-ROM.
Windows 95: If you are using Windows 95 release 1, you willhave to provide your own boot disk. 'Good' news: Since Win95 onlysupports FAT16, you can use your old DOS boot disks for this.
Boot off the floppy. If this disk has CD-ROM support, you maywish to hit <F5> to keep from loading it -- we won't use it on thisboot
If appropriate, FDISK the drive, create your partition, make it 'active'
Windows 95r2 & 98: If you run FDISK and have a hard diskbigger than 512M, you will be asked if you want to use FAT32. I recommendyes, do use FAT32. I have *never* come across an application whichdoesn't work with FAT32, only a couple utilities that normal people wouldbe better off without. If your primary purpose is games and recreation,this may not apply -- games are more picky than business apps. FAT32lets you use larger hard disks as one partition, and stores data much moreefficiently than FAT16 does.
After FDISKing the drive, you need to reboot the machine, booting offa disk with CD-ROM support.
Format the hard disk, using
FORMAT C:/S
This not only formats the hard disk, but puts a system on it so itcan be booted.
I have been told that I should say here DON'T REBOOT YOUR SYSTEM YET!(Hi, K.O.B.! 8-)
Step 3: Copy the installation files
Go to drive C:, and create a directory called C:WINDOWSOPTIONSCABS. Note, this has to be done in three steps, you just can't make all threenested directories.Commands for the DOS command line challenged: You type the stuff in lower case and Italics
A:>C:
C:>md windows
C:>cd windows
C:WINDOWS>mdoptions
C:WINDOWS>cdoptions
C:WINDOWSOPTIONS>mdcabs
C:WINDOWSOPTIONS>cdcabs
C:WINDOWSOPTIONSCABS>
Excuse me, that's one convoluted directory path! Where did you comeup with that brain dead location?
No arguments...it is a pain to type. However, somehow, it becamea standard location to put these files. You can put them anywhere,but if someone who knows Windows sits down in front of your machine, theywill probably think to look in this location. On more than one occation,I didn't notice that someone put them in a DIFFERENT location. MostOEMs use this location. If you wish to be a free thinker, I wouldsuggest, rather than messing with this, try a REAL operating system, suchas Linux or OS/2Copy the contents of the WIN95 directory on the CD-ROM to this directory.
C:WINDOWSOPTIONSCABS>copyd:win95*.*
Or, if loading Windows 98,
C:WINDOWSOPTIONSCABS>copyd:win98*.*
When this is done, eject the floppy and reboot your computer.
Step 4: Run SETUP
At this point you machine should be booted from the hard disk. Nodevice drivers of any kind should be loaded. There should be NO CONFIG.SYSor AUTOEXEC.BAT file. This is a clean boot. You don't wantWindows to mess up and try to keep anything you have already loaded. This particular re-boot is very critical -- if you booted off the floppy,Windows Setup will assume you will continue to boot from the floppy, andfunny things will happen later.After the machine has rebooted, go back to the C:WINDOWSOPTIONSCABSdirectory and type SETUP.
C:>cd windowsoptionscabs
C:WINDOWSOPTIONSCABS>setup
At this point, the Windows 9x startup program will start.
Windows 95, both releases: The first complication is when SCANDISKruns, the first part of the setup process. It will complain thatthe system does not have HIMEM.SYS loaded, and thus can't run. Thisis quite O.K., as your hard disk has just been wiped out, and if somethingcorrupted the hard disk so far, you have hardware problems. Tellthe system to continue anyway. Windows 98 doesn't seem to have thisproblem, interestingly. If you have a very small hard disk, you maynot see this message.
There are a few other points of interest. Setup *may* willask if your system has a CD-ROM, a Network card or a sound card. General rule: Don't select ANY of these, even if you DO have anyof those devices.
WHY?
Windows 95 was developed in 1994. At that time,many or perhaps even most CD-ROMs were propriatary, not IDE or SCSI. Many odd sound cards existed, as did many odd network cards. By checkingany of those options, you are telling Windows to do a more complete scanfor these devices. This not only slows down this step, it also GREATLYincreases the chances the system will hang by 'probing' for one deviceand crashing another device, and thus your computer.If you have an IDE or SCSI CD-ROM, it will be foundanyway.
If you have a Plug-and-Play sound card or networkcard that is supported by Windows, it will be found anyway.
If you have a device NOT supported by Windows, Plug-and-Playor not, checking these boxes won't help.
In short, in setting up a modern machine, checkingthese boxes will only hurt, not help. IF you are using an old propiataryCD-ROM (i.e., Teac, Soundblaster 2x, Mitsumi 1x, etc.), you might gainby checking the CD-ROM box. If the system locks, hey, I warned you.
At one point, Setup will ask you where you wish to install Windows. NOTE it wants to put it in C:WINDOWS.000. This is bad. Choose'Other Directory', and change it to C:WINDOWS. Windows will protestand complain, that's o.k., tell it to do it anyway.
WARNING: Make sure you delete the period! In theory, 'C:WINDOWS'and 'C:WINDOWS.' (see the period?) are the same location, although someprograms will go absolutely bonkers if you leave that period in there. Ask me, I know.
Let the install complete, and reboot as needed.
Step 5: Cleanup
Whaddya mean cleanup? Aren't we done??
Nope. If *all* your hardware is recognized by Windows 9x directly,you are done, but that is pretty rare.Go to the System Control Pannel. Look under Device Manager. You will very possibly see a yellow question mark labled 'Other Devices'. This is where Windows 9x Setup filed all things it noticed but didn't recognize. These devices are known, but no drivers were loaded. Usually thereis a semi-descripive title, such as 'PCI Ethernet card' or 'SCSI Adapter'. You may see some devices labled 'Unknown device' -- save these for last. Or ignore them. I haven't figured out why some main boards put thoseup -- sometimes, they may be USB ports, other times, they are bizzare functionson otherwise plug-and-play cards (One of the many variations of the Soundblaster16 board leaves two mystery 'Other Devices' at I/O address 100 and 101which can be ignored)
There are two things you can do here: 1) pick the device, andclick 'Change driver'. Insert the disk or CD-ROM, and point the systemto the drive and the proper driver. Option 2) Delete the device,and let Windows notice it on the reboot, and install the drivers then.
Note that if you try to install video, sound or network card driversbefore doing this, you will probably fail. Why? Because the'resources' used by the cards in question are already in use by these 'OtherDevices'. You can't load two devices using the same resources, thereforeyou can't load the drivers before you remove them from 'Other Devices'.
Once this is done, if you are snug on disk space, you can delete *.EXE,*.BIN, and basicly everything but *.CAB from the C:WINDOWSOPTIONSCABS
Why?
Well, those files won't be used again, unless you need to reinstall Windows,of course. And, of course, if you DO have to re-install Windows,you will need to copy those files back, so I don't recommend deleting themunless you run snug on space.You want to leave the *.CAB files so the system can find the files everytime you add or remove something. Yes, this means you have a copyof absolutely everything on your hard disk, and two copies of the thingsyou are actually using. Microsoft efficiency.
I don't like the Microsoft client software for several reasons. 1)it doesn't support NDS (Netware v4) well at all. 2) It hastraditional Microsoft disrespect for network security (it will commonlyspontaniously connect to servers, and it has been seen to do so as a passwordedsupervisor equivilent. Not funny.)
I instead recommend that you use the Novell client. This is abit tricky. Easy and works well if you go through the right process,but a nightmare if you don't.
The short version:
1) Get Microsoft Network Support working
2) Delete the excess
3) Log into the Netware network
4) Install Novell Client Software.
5) Adjust client software, and reboot.
Step 1: Get Microsoft Network Support working first.
If it is not already done, load the network card driver. As partof this process, it probably loaded the Client for Microsoft Networks andClient for Novell Networks, along with NetBEUI and IPX/SPX protocols, andperhaps Dial-up Networking Adapter and TCP/IP. If not there, loadat least the IPX/SPX and Client for Novell Networks.This leads to mistake number 1: If you want to hook to a Novellnetwork, you would think you might click on Add, Client, and for Vendor,you would pick 'Novell'. Wrong. You are NOT (initially) loadinga Novell provided client, you are loading a Microsoft-provided client fora Novell network. Got it? The options under Novell are theDOS-based client solutions. YES you are connecting to the Novellnetwork, but not by using Novell solution -- not yet.
Set the Primary Network Login to Client for Netware Networks.
Step 2: Delete the excess network components
If you don't absolutely NEED NetBEUI, remove it. It is a brain deadMicrosoft protocol and inapproprate for large offices.If you aren't using a modem or internet dial-up, remove the dial-upadapter.
If you aren't using TCP/IP, you may wish to remove it.
If you aren't using NT or Windows 95 peer-to-peer networking, removethe Client for Microsoft Networks. (some Internet packages expect thisto be there. If you need it, leave it.)
The less you have loaded, the fewer problems you will probably have.
The system will want to reboot after removing or adding anything.
Step 3: Login to network
When you reboot, you *should* get a three-field box, asking you for a username, a password and a server. IF you do not, your network softwareis not working properly, or you forgot to plug in your network cable. IF you didn't get the login box, you have to figure out the problem andfix it before going further.Note, if you are running Netware v4.x, you are logging into your networkin the Bindary Emulation context, for you are not coming in as a NDS user. Make sure the user ID you are coming in as exists in that bindarycontext. Your login script probably didn't run, your drive mappingsare probably messed up. That's all o.k. This is only temporary.
If you get in successfully, you have proven your hardware configurationand your network card driver is working properly (if not, fix it!).
Step 4: Load Novell's Netware Client
There have been several versions of Novell's client software. Entertainingly,they keep changing the name. Roughly in order, it was Client 32,IntranetWare Client 32, Client 32 for Windows 95, Novell Netware Client.I would recommend Novell's Window Client software v2.1 or later (theversion number is displayed in the Network Control Pannel when you doubleclick on the Netware Client line. If it doesn't come up with a versionnumber, it is older than v2.1).
Windows 98: Use client 2.5 or later.
Update: I have played with v3.01. Skip it. v3.10has been released -- looks nice. Works well so far.
Update: Gained more experience with client 3.10. It works well,but it has lots of 'extras' which probably don't do much for most peoplerunning Netware v4 or earlier, so I am personally keeping v2.5 around forolder computers. IF you aren't using TCP/IP networking, you may wantto customize your setup, and tell the client software to use IPX only.
Yet More Update: Client 3.1 does NOT work with the original release1 of Windows 95. You either have to patch Windows 95 or use client2.5.
Update for Windows 98: I -- and many other people -- havediscovered that under some cirumstances, it is not possible to installthe Netware client from the server. The short version of the problemis the client disconnects you from the server while doing the update, preventingthe rest of the update from completing, and leaving a real mess. Solution: 1) Load the client from a CD-ROM (a problem if you don't havea CD-ROM burner) or 2) copy the client to the local workstation FIRST. Then, follow these directions from THIS directory, rather than from theserver. The v3.x client sometimes puts up a warning message to thiseffect, unfortunately, I haven't had it happen to me in the lab, just atclients, where I am ill-prepaired to play with it. There is apparentlya 'fix' for this problem, apparently involving a new file from Microsoft,but Microsoft doesn't consider it a 'standard' fix, so they don't havethe file for public distribution. The Great Bill has spoken. I create a directory on the local hard disk, C:NovellIns tocopy the install files to, but there is nothing sacred about this.
I normally copy the Novell client software to the SYS:PUBLICCLIENTWIN95directory on the server. Yeah, it seems kinda dumb to put the clientsoftware on the server you are trying to get to, but since both Windows9x and Windows NT both have a limp-on mode for Netware, it actually workspretty well.
In either event, browse/explore/whatever your way to the client directory,and run SETUP.EXE from this directory. There are a lot of files here,so I normally just tap the 'S' key -- all versions of the client softwareI have used take you right to the SETUP.EXE file when you do this.
Some versions of the client software offer you the chance to upgradeto the Novell ODI drivers from the Microsoft NDIS. This sounds like a goodidea -- Novell's ODI spec is more rigidly controlled than Microsoft's NDIS,and under DOS, ODI was much easier to use and troubleshoot. Thisisn't true under Windows 95, however. Everyone's Windows 95 NDISdriver works, that can't be said of the 32 bit ODI drivers. In general,I would recommend UN-checking this box. This can also simplify futuretrouble shooting, should problems arise later. This option has beendropped from later versions of the driver software -- probably good.
Unlike most programs, it seems best to accept the defaults for the Netwareclient software (other than the above issue with the ODI driver)
Update: The client v3.x defaults to TCP/IP as its prefered protocol,and loads something called 'Novell Distributed Print Services'. Iusually turn both of these off, but the default does work fine.
Usually, at some point in the process, it will ask for the Windows 9xinstall CD-ROM. When it comes up with a location box, hit the upor down arrow until you see the (way) above C:WINDOWSOPTIONSCABS.
5) Adjust client software, and reboot
Now, when the client software finishes installing, you are asked to reboot. Don't. Not yet. Some versions of the client software installeroffer to let you customize the installation, others just let you deferthe reboot and return to the Windows desktop. Either way, work yourway to the network control pannel, and double click on the Novell Clientservice to customize it. There are two key things you MUST change:under the Default Capture tab, turn OFF the Form Feed and the Enable Bannercheck boxes. Idiotic feature that has been the default in Netwaresince day one. While many mainframe systems use banners quite effectively,I haven't seen any networks using them. Ever. I've beenplaying with Netware for 13 years, and the most common problem is the bannerpage at the front of a print job, and the blank page at the end.Update: Client v3.01 and v3.10 have FIXED this!! YEAH! Then they turned on the Notify option. Bummer.
IF you are running NDS (i.e., Netware v4), you should know that whateverserver you specified when you first logged in under the Microsoft clientsoftware is now the default server. This may not be appropriate. In theory, you want to log into the tree, not the server. In practice,unless you disable the NDS support on the client, you WILL attach to thespecified server, then from there you will log into the tree. Ina small network, there is no reason to change anything. In a bigor multi-server network, you will find it best to reset the default loginto the TREE, not a particular server, in case that server is down, overloaded,or gets replaced.
Now, you can reboot. You now have a functional Windows 9x workstation! You will probably now need to set up printers, but that's another story...
Backto Computer Opinion Page
(C)opyright 1999 Nick Holland
Windows 95 OSR 2.5 : CD Key: 24796-OEM-0014736-66386Windows 95 OSR 2.5 Addon : CD Key: 24796-OEM-0014736-66386
Windows 95 plus pak : 28876-062-0805825003490
Windows 95 v4.00.950 : 24264-425-4287696-06468
Windows 95 v4.00.950 R2 : 875-7215850
Windows 95 v4.00.950 R3/R6 : 975-4769754
Windows 98 Build 1708 : CD-Key: BBH2G-D2VK9-QD4M9-F63XB-43C33
Windows 98:HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 Upgrade:BMFGB-92WFM-GFDXD-FQGW6-WT47P
Windows 98 OEM:FT9CH-XVXW7-7BFCM-RPR49-VDHYD
Windows 98 Retail:F73WT-WHD3J-CD4VR-2GWKD-T38YD
Windows 98 SE:HF928-QG627-23QDB-PY4YF-B8GMG
Windows 98 SE OEM:FT9CH-XVXW7-7BFCM-RPR49-VDHYD
Windows 2000 Professional : s/n : HRTHC-WWDF2-JQHRY-XK8X3-DTDW6
Windows 2000 Pro:TQ4CV-XPJR3-KPG3Q-HGH74-BMYWT
Windows 2000 Server:H6TWQ-TQQM8-HXJYG-D69F7-R84VM
Windows 2000 Server : s/n : MQRJT-48J9R-36JXB-HJFCJ-TQXDQ
Windows 2000 Adv Server:KRJQ8-RQ822-YRMXF-6TTXC-HD2VM
Windows 2000 Advanced Server : s/n : JJRJJ-6Q7FV-D4W8V-MKT2Y-G499Q
Windows 2003:K4RBR-F3K42-M9RXG-48TPR-H6BPB
Windows 2003 Server:JB88F-WT2Q3-DPXTT-Y8GH8-7YYQY
Windows 2003 Web Server42X8-7MWXD-M4B76-MKYP7-CW9FD
Windows ME:RBDC9-VTRC8-D7972-J97JY-PRVMG
Windows Me Professional:975-4769754
Windows NT 4.0:s/n: 227-075-455 cd key : 419-0201344
Windows NT 4 Workstation OEM:34997-OEM-0028594-50108
WINDOWS NT 4.0 SERVER 4.0:419-0104153
Windows NT Workstation 4.0:s/n: 807-2414712 or
OEMs/n: 28997-OEM-0025957-49297 or s/n: 425-1921701
Windows XP Home:BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Windows XP Home SP2:J76RR-MY44M-VTJ9T-6PMWX-FH88T
Windows XP Professional:FCKGW-RHQQ2-YXRKT-8TG6W-2B7Q8
Windows XP Professional SP2:P7WDR-H2CHK-X8V26-7TQTV-DRM4D
Windows XP Corporate:TGRH7-K6QR3-RT6J4-V36FP-869HT
Windows XP 64-Bit:b2rbk-7kpt9-4jpgx-qqfwm-pjdgg
Windows XP Home OEM for Dell PC:FP2TC-MJ2CP-32J8T-FP3BY-RW6K6
Windows XP Media Center 2005: C4BH3-P4J7W-9MT6X-PGKC8-J4JTM
Windows XP Media Centre Edition 2005 QKRX4-WP7HT-YQMBW-GTDQD-7MY42
Windows XP Media Centre Edition 2005: JJKB2-W3444-G8Q49-MH8R9-MD7PQ
Windows XP Media Centre Edition 2005:
JJKB2-W3444-G8Q49-MH8R9-MD7PQ
C82GJ-YH627-72GBT-R7XV7-M7Y4B
C4BH3-P4J7W-9MT6X-PGKC8-J4JTM
RD6W4-369DT-DMHQH-4RVKW-WY6PG
KCQ9Q-FTBM4-6HTWV-M7DKM-T4BFB
QKRX4-WP7HT-YQMBW-GTDQD-7MY42
C4BH3-P4J7W-9MT6X-PGKC8-J4JTM
Windows LongHorn ProfessionalPTWG-M9PGK-2HT2J-JT9R9-6V8WM
WINDOWS Office all:
Windows Office 95:411-0250
Windows Office 97:0401-1234567
Windows Office 97 Standard:4657-1931151
Windows Office 97 Professional: 0401-1234567
Windows Office 2000:GC6J3-GTQ62-FP876-94FBR-D3DX8
Windows Office 2003:GWH28-DGCMP-P6RC4-6J4MT-3HFDY
Windows Office 2004V7HF-HP2FX-MM433-JPCJC-YW68G
Windows Office XP:FM9FY-TMF7Q-KCKCT-V9T29-TBBBG
Windows Office Professional Plus 2007 – MTP6Q-D868F-448FG-B6MG7-3DBKT
or TT3M8-H3469-V89G6-8FWK7-D3Q9Q
Windows Office Visio® Professional 2007 – QB6MH-Q82HX-BFWPK-8TXTY-HHJT6
Windows Office OneNote® 2007 – TFKGD-9VXBG-T22DK-FQB9P-MBPG6
Windows Office Project Server 2007 – BWPMX-XY8XF-KGBQ6-XKT8R-GHXD3
Windows Office Project Professional 2007 – GP24P-FC3DP-HXY7Q-YG3JR-J4G3G
Windows Office Groove® 2007 – R83W8-GJQ82-GJ378-XQW9W-JBYKT
Windows Office Groove® Server 2007 – PGT8R-VBMBC-6V7GY-TW3HT-8FP36
Windows Office SharePoint® Designer 2007 – VQCR8-6KP8Q-Y2FTW-3YQD7-R22G6
Windows Office SharePoint® Server 2007 Enterprise – FDJDK-66WCT-2HD9C-4TY63-38C4G
Windows Office SharePoint® Server 2007 Enterprise(x64) – FDJDK-66WCT-2HD9C-4TY63-38C4G
Windows Office Forms Server 2007 – FDJDK-66WCT-2HD9C-4TY63-38C4G
Office Forms Server 2007 (x64) – FDJDK-66WCT-2HD9C-4TY63-38C4G
Windows Access Menu v3.5 : Name: Terry Georgi Code: WAM354657272792047656F726769
Windows Draw by Micrografx : s/n: DV1001LXX10827
Windows Enforcer v3.0 : 5434343543435431354
Windows for WorkGroups v3.11 : s/n: 18016-010-0187302 or s/n: 19492-020-0028353 or s/n: 511807955
Windows for workgroups v3.11 SPANISH : 872-0298-300C
Windows Help Maker II v2.0 : Name: Dilburt^ LSD s/n: 2310027996
Windows Interactive Network Server PE v6.0: Enter all 1's
Windows Lock v2.2 : 26384094848499
Windows Lotto Pro v4.01 Win95/NT : Name: GREENBACK s/n: F7F7556C86E762EB
Windows Lotto Pro v4.02 : User: UNC Team s/n: F58B8FC5D18F3F90
Windows Lotto Pro v4.02 : Name: LOMAX [DSI] s/n: 49877C05F4611AC0
Windows Lotto Pro v4.03 : Name: UNC TEAM s/n: F58B8FC5D18F3F90
Windows Lotto Pro v4.04 : Name: United Cracking Force - QT s/n: 484D401F59643C08
Windows Multi-Lock v1.1 : 2643985749399
Windows Multi-Lock v1.2 : 2643985749399
Windows Me : CD Key : B6BYC-6T7C3-4PXRW-2XKWB-GYV33
Windows NT 4.0 Workstation : 425-1921701
Windows NT Server 4.0 Server : CD-Key: 427-5632883
Windows NT Tips, Tricks, and Registry Hacks : Name: SpiNBalL s/n: 4CA0A9AE
Windows NT Workstation 4.0 : CD-Key: 09496-0009552-77303
Window On Wallstreet Internet Trader Pro v7.0 : s/n: ZRL0NXM4NLG75AN8H6SRP3
Windows Picture v1.1 : Key: 5173e7bd17
Windows Scanner v1.0 : s/n: 257-1184-WSC-32
Windows Scientific Calculator v4.0 : Name: bLACK tHORNE / MCC s/n: 12210743399
Windows Security Officer 98 v3.5 : Code: 9951262350
Windows Security Officer 98 v3.6 : Code: 9951262350
Windows Task-Lock v4.0 : single license: 45687897134654084487080 multi-site: 418117113408700703414174
Windows Time Lapse Video V1.3 : s/n: 04391962
Windows XP Home : CD Key : KQXXH-YW4QM-B84W8-296FX-6XRDW
Windows XP Professional : CD Key : FCKGW-RHQQ2-YXRKT-8TG6W-2B7Q8
Windows XP Professional SP1 : CD Key : 7QVT6-T2738-WRKJB-YKRFQ-XVK98
WinDoze WakeUp v1.41 : Name: Delphic Code: 33-35-39-42-41-43-43
WinDraft v2.05 : Unlimited: CHN-T20-NST-6T3-L06-NO
Windrop v3.3 : Name: el loco Company: Boedha Code: CORE-199833000000-3051
WinEaze v1.4 for Windows : Name: The Olympus Gods s/n: OZ87C51555
WinEdit Pro v3.10 for Windows 95 : id: 281317 s/n: AG01DQUX or id: Pantera s/n: 1G34DJS9
WinEdt32 v1.414 : Name: Denis Grondin Code: 38477750
WinEDIT 98 v52298 : Name: WinEdit96 ID: 304407 s/n: DG01JJJ3
WinExit 95 V3.1.27 : Name: SiraX Code: 1507328
Win Expose-I/O +v2.00 : Name: TwinHead [uCF] !96 Company: United Cracking Force addrLine1: (C)racking 1994-1996 addrLine2: UCF s/n: 1996 Key: f41dd7e2
Win Expose-I/O +v2.00 : Name: MarQuiS Company: CYC addrLine1: 1 addrLine2: 2 s/n: 3 Key: EXPLFA576734
Win Expose-I/O v1.x : Name: MarQuiS Company: CYC AddrLine1: 1 AddrLine2: 2 s/n: 3 Key: EXPLFA576734
Win-eXpose-I/O v2.0 : Name: LiGHt DRUiD Company: iSS'99 AddressLine1: light_druid@hotmail.com AddressLine2: fuckyou@suxx.com s/n: (None) Password: f41c3c94
Win-eXpose-Registry v1.00 : Name: n03l Company: Faith2000 Address Line 1and 2: Faith2000 s/n: 2468024680 Password: f4004298
WinEye v3.0 : Name: FUTUR2000 Code: 66282323430
WinEye v3.1 : Name: Arfa [PCY] Code: WE31-9DEDFB7A584CA85E
WinEye v3.1a : Name: N!P [GCK] Code: WE31-1B64E35DF70707CF
WinFax Network Server v4.1 : Server No: 1161-3469-8496 User Count No: 1501-9895-6835-8003
WinFax Pro for Windows : s/n: 1321-2123-7176 or s/n: 1331-7470-0001
WinFax Pro v3.0 for Networks for Windows: s/n server: 1100-0955-4806 or s/n user: 1152-3481-1788
Winfax PRO v3.0 for networks for Windows 1: server: 1100-0955-4806
Winfax PRO v3.0 for networks for Windows 2: user: 1152-3481-1788
Winfax PRO v3.0 for networks for Windows 3: user: 1152-7632-1646
Winfax PRO v3.0 for networks Windows : server: 1100-0955-4806
Winfax PRO v4.0 for networks for Win : server: 1101-3405-1357
WinFax Pro v4.0 for Networks for Windows: s/n server: 1101-3405-1357 or s/n user: 1154-2501-7095 or s/n user: 1154-3403-4849
Winfax Pro v7.0 for Win95 : 7410-2151-7186 or 7420-4071-4667
WinFax Pro v7.0 for Windows 95 : s/n: 7410-2151-7186 or s/n: 7410-4085-4233 or s/n: 7420-4071-4667
WinFax 8.0 PRO : s/n: 12-31-90006-GE
WinFax v9.0 : Name: SimpsonINC s/n: NJQAEYLKSX
WinFish1 Lake Fishing v1.2 : Name: DSG TeAM Code: WF473341LF
Winfit v2.5 : s/n: 1006775544
WinFlash32 4.0 : Name: SRegistered User s/n: 196700625
WinFlash Administrator v5.1 : Name: Jerry Rogers s/n: 15B56C000676
WinFossil/32 v1.04 for Win95 : Name: The GuaRDiaN aNGeL s/n: 36147306
WinFossil/32 v1.04 for Windows 95 : Name: The GuaRDiaN aNGeL s/n: 36147306
Wingate v1.3 : Name: tHATDUDE! Reg: t00l.00</FONT><v00'*001
WinGate v1.3 for Windows 95 : Name: Misha [UCF] s/n: l11*p99,499`*66l
WinGate v1.310 : Name: Byte Ripper s/n: 78A98F5F512243C15667015A or Name: Phrozen Crew 96 s/n: 1937157FDFE06A1AECF56D0B or Name: tHATDUDE s/n: E3353EAEC806A6946A85FD46r or Name: TKC s/n: 4E993AA3869CF655C9C17D06
WinGate v1.311 : Name: DjPaul [uCF] s/n: F504EAB1B0218261BE648134
WinGate 2.0 Lite : Name: warez License: 8E63FC122CB486AE534FF698 (5 users)
Wingate 2.0 Pro : s/n: 1bcc8d7f52067346317d05eb (unlimited users)
Wingate 2.1 beta2 For Windows95 : Name: Leddy / 2000AD s/n: 729E0308620B2D1779234376
WinGate v2.1b for Windows 95 : Name: mRFANATIc [DEMiSE] Key: 8DB730C21F2E035C76F16712
WinGate 2.1 Pro : Name: iBC s/n: F0271B3DE5A25F918BB17D2A
Wingate 3.0 Beta8 : Name: Leatherman/2000ad Lite: 2 Users: 8332B9CE9FFA0BA30800E35C 5 Users: 8332B9CE0DFB0BA3A407E55C 10 users: 8332B9CE4EFC0BA33008B05C Unlimited: 8332B9CEEEFD0BA3D0FDAA5C Pro: 2 users: 8332B9CEA4FE0BA3600080DC 5 users: 8332B9CE09FE0BA30407C4DC 10 users: 8332B9CEFBFF0BA39608EEDC Unlimited: 8332B9CE59FF0BA382FDA1DC
Windows 95 Osr 2.5 Iso Cleanroom
WinGate v3.0 RC1 : Name: WinGate 3 beta tester 255 Users: F3A6C7BA709A7CB46C5F5E13
WinGate v3.0 Pro : Name: Boedha Code: 683A1B8A57AFEB951529B6E8
WinGate v3.0.2 : Name: James Bond s/n: 69D5EE2F11D34D809065CE4A
WinGate vX.X : Name: United Cracking Force - QT s/n: 419764B050C2EF1DD21CAB12
WingDate v4.2 : Code: WDAT00100010007
WinDesk Tools v2.1 : s/n: 19431943
WingDir 4.5a for Win95/98/NT : s/n: WDIR04506029630
WingDir v4.6 Win9xNT : Code: WDIR00100010007
WinGO Folder Alias v1.6 : Name: Norway Company: Revolt98 s/n: 562526-97151458-BM
WinGo v1.6.74 : Name: wizdaz Company: Warp s/n: 342353-332497481-DC
WingPager v1.0.120299 : Name: TL]KfNVR Code: #27#30#25#45#25#40#24#31
WinGrep v2.00 : Name: dustie of blizzard Code: 656C7669732F
WinGrep v2.1 : Name: draXXter s/n: 656C7669732F
WinGrep v3.0 : Name: John Bar Code: 656C7669732F
WinGroove v0.9 : Pass: ZAAAAAAA userid: BJG7010e Pass: ZAAAAAAA userid: BJG70109
Wingroove v0.9E : First box: ZAAAAAAA Second box: BJG70109
WinHacker 95 2.0 : Name: -= +ALI-BABA =- Company: D4C / 1997 s/n: 826d-7b7942
WinHack2.0x : Name: MIRAMAX Company: The Force Team s/n: 7221-8ccbe1
WinHacker 95 2.01 : Name: Clark Kent Company: Daily Planet s/n: f023-1581c7
WinHex v7.1 : Code 1: 49725 Code 2: 35780
WinHex v8.0 : Code1: 49725 Code2: 35780
WinHex v8.01 : Code1: 49725 Code2: 35780
WinHex v8.02 : Code1: 49725 Code2: 35780
WinHex v8.10 : Code1: 49725 Code2: 35780
WinHex v8.23 : Code1: 49725 Code2: 35780
WinImage +v2.5 for Windows 95/Windows NT: Name: The GuaRDiaN aNGeL s/n: 8CA2D0D9
WinImage 2.10a : Name: Registered Version #: 8BDCDD26
WinImage 2.20-2.51b4 : Name: WINIMAGE s/n: CEE5D8
WinImage 2.x : s/n: 3B05ED64 4C0806AC Name: MarQuiS [UCF]
WinImage v2.1/2.2 : Name: Registered Version s/n: 8bdcdd26
Winimage v2.25b3 : Name: Registered Version Code: 8BDCDD26
WinImage v3.0 for Win 3.1 : Name: WINIMAGE s/n: CEE5D8
WinImage v2.5 for Windows(95/NT) : Name: TeLLeRBoP s/n: 214326F
WinImage v3.0 for Windows 95 : Name: BEL!AL '96 Code: 13F37020
WinImage 4.0 : Name: CRACKED s/n: 741DB3
Win Image 4.0 : Name: Hacker s/n: 5B5162
WiNiMAGE v4.0 PRO MULTiLANGUAGE : Name: John Hunt s/n: 122CA601
Winimage v4.0.4008 : Name: GLoW eXzibiT s/n: 31AE869C
Win Image v4.0.4009 : Name: Capoeira/TS s/n: 10C3528E
WinImage v5.00.5000 : Name: draXXter [Faith2000] s/n: D2CE2812
WinImages 4 : Lighting: 1614-4726-3242-5061 Plasma: 4813-7113-2715-4376 Blur: 4303-6813-6657-8168 Geom: 8002-6046-2672-5442 Pattern: 1385-7568-6450-6122 Filter: 8542-0003-0007-2153 Math: 3862-0650-3571-7804 Collage: 7734-6687-7151-8367 Standard : 2037-5234-0118-3682 Alpha: 2481-6884-8618-0478 Morph: 6784-7081-8063-2208 Art: 0837-3268-7828-2281 Photo: 0703-0714-1068-7663 Video: 7487-1312-1336-2361
WinImages v4.5 : Lighting: 1657-6021-5842-5257 Plasma: 0386-2352-0363-3724 Blur: 0086-7112-7223-2238 Geom: 6083-5362-8546-3208 Pattern: 6083-0806-7388-4247 Filter: 4485-0860-7848-2457 Math: 8342-3342-1314-6348 Collage: 3368-0110-4648-1073 Standard : 7005-2446-0771-8453 Alpha: 7620-5405-0635-1061 Morph: 4133-7108-2438-8242 Art: 2666-6871-1753-4382 Photo: 3043-0300-5057-4863 Video: 3715-5274-0553-0760 Attrib: 5571-2224-8340-7784
WinImage Ver 8.0 Hot
U should know this floppy expert!
(Name: Cyberloner S/N: 783C9E2)
Winfo v2.0 : Name: bUrnoUt s/n: 209349220464
Win Lotto Pro v4.04 : Name: Versus Cracker Code: 6BAC295D9E391618
Win Lotto Pro v4.05 : Name: Registered User Code: 6FEC7560003FC762
Winlpd v1.0 Build 1004 : s/n: 1234-1234-1234-1234 Key: 59DC-B3B8-6770-CEE0
WinLPR v1.60 : Name: Decline/Laxity s/n: 689-881-390-494
Win Manager 2.50 : 05529
WinMaster v1.5 for Windows : s/n: 4010625852V01
WinMOD v1.1 : Name: Azrael [PC] Code: 27?051
WinNavigator v1.30 : Name: fallen s/n: 214567
WinNavigator v1.35 : Name: fallen s/n: 214567
Win Navigator v1.50b : Name: fallen s/n: 214567
WinNC v1.5e : Name: escom/CORE s/n: uj996ZLYGB
WinNC v1.5 Professional : Name: Dannie DaCarder Code: vERcPkLA2E
WinNFS V.3.3a for Win95 : Name: blastsoft Company: blastsoft s/n: 1133345699
WinOnCD To Go! v1.3 for Windows : s/n: 00246-94392401i
WinOnCD To Go! v1.4 for Windows 95 : s/n: 00246-46394903F
WinOnCD v2.14 for Windows : s/n: SWFOWIN1-214-30608
WinOnCd v3.0 : 00946-80026090n
WinOnCD v3.5 : s/n: 01046-29312833k
Win On Cd v3.5 OEM : s/n: 01046-51744895d or s/n: 01094-59482439o
WinOnCD v3.6 Build 399-2 : s/n: 01551-06845806o
WinOnCD v3.6.408-1 : s/n: 01510-30673562k
WinPac2 (32bit) v1.00 : Name: Wayne Kerr Code: 99198-28732-69791-65148
WinPac 2 v1.01 : Name: LOMAX s/n: 59808 82380 10022 15131
WinPatch v1.1.01 : Name: aKIRA sAKE pin: L&D-0626-20493290 org: japanese arts of fighting or Name: tKC/PC 98 pin: L&D-0626-15281175 Org: Phrozen Crew
Win Patch v1.2 : Name: VERSUS '98 pin: L&D-0611993618007 Company: REKiEM
WinPatch v1.2.1 : Name: MANiFEST pin: L&D-0611-14784821 Company: DESTINY
WinPatrol Ver 9.7.X.X
Great utilities to block bad software
(Name: Cyberloner S/N: 7J33864007)
WinPGP v4.0 : Name: tHATDUDE! Last Name: Cracker Reg: 273495638
WinPGP v4.1 and v5.0 : Name1: Registered Name2: Copy s/n: 291191258
Winplay 3 v2.0 : 100011-301000-5000
WinPlay 3 MPEG Audio Player : Name: (anything) Code: 222221-025226-0222
Download Windows 95 Bootable Iso
WinPlay MP3 Player v2.0 : Registration Code: 100011-301000-5000
WinPlay3 MPEG Audio Player : Name:CracK Da WareZ s/n:222221-025226-0222
WinPlayer 3 v1.0 MPEG Audio Player : s/n: 1234DA75901230
WINPLAY3 : s/n: 100011-301000-5000
WinPlus v3.06.2 : user Name: GLOU Company Name: GLOU (Launch WinPlus, In Welcome display box press the Purchase Button)
WinPoint 95 final beta : Name: RyDeR_H00k! [UCF] s/n: 7C3D5C1B
Win Poly Grab : s/n: WPG-01-002336
WinPop Plus v.1.0 : Name: michael shelby Key: 18027F74
Winpop Plus v1.0 Build 144 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.0 Build 145 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.0 Build 148 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.0 Build 149 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.0 Build 150 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.0 Build 152 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.0 Build 154 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
WinPop Plus v1.0.100.156 : Name: CORE/ITR Small Office: 701A6679 Pro: 6D1D184B
WinPop Plus v1.0 Build 160 Win98/NT : Name: Blackstar TRPS98 s/n: 13741C1A
WinPop Plus v1.0.100.161 : Name: michael shelby s/n: 18027F74
WinPop Plus v1.0 Build 162 Win98/NT : Name: Blackstar TRPS98 s/n: 13741C1A
WinPop Plus v1.0 Build 163 Win98/NT : Name: Blackstar TRPS98 s/n: 13741C1A
WinPop Plus v1.2.100 Build 100 Win98NT : Name: Blackstar TRPS98 s/n: 13741C1A
WinPop Plus v1.2.100 Build 101 Win98NT : Name: Blackstar TRPS98 s/n: 13741C1A
Winpop Plus v1.2.102 : Name: Versus s/n: 3F0A121D
WinPop Plus v1.2 Build 103 Win98/NT : Name: Blackstar TRPS98 s/n: 13741C1A
WinPop Plus v1.2 Build 104 Win98/NT : Name: Blackstar TRPS98 s/n: 13741C1A
Winpop Plus v1.2.106 : Name: Versus s/n: 3F0A121D
Winpop Plus v1.2.107 : Name: Versus s/n: 3F0A121D
Winpop Plus v1.2.109 : Name: Norman Vialpando s/n: 3F163E56
Winpop Plus v1.3.100 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Winpop Plus v1.3.103 : Name: Norman Vialpando s/n: 3F163E56
Winpop Plus v1.3.106 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
Windows 95 Osr 2.5 Iso
Winpop Plus v1.3.108 : Name: CORE/DrRhui Small Office: 11682279 Pro: 0C6F5C4B
WinPop Plus v1.3.115 : Code: 30106F1E
WinPop Plus v1.3.119 : Name: Blackstar TRPS98 s/n: 13741C1A
Winpop Plus v1.3.120 : Name: LordFritz/MANiFEST s/n: 64057466
WinPop Plus v1.3.123 : Name: Blackstar TRPS98 s/n: 13741C1A
Win Port v4.05 for Windows and DOS : s/n: B306430-HCMJ
Win Port v5.0 2 User Server/Clients : s/n: AAC103427-eefseh
WinPowerDown v1.12 : Name: Wrong registration code! Code: E34CD729E72037CC40C342C259BC77859E61B8BD53A664BEB1
WinProbe 95 : 022-18c-96622..
WinProbe v3.0 for Windows 2 : 00087228DH9
WinProbe v3.0 from LandMark for Windows: s/n: 00065088DH9 or s/n: 00087228DH9 or s/n: 37809H9
WinProbe v3.1 for Windows 2 : 65088DH9
WinProbe v3.1 for Windows 3 : 0000000000
WinProbe v3.1 from LandMark for Windows: s/n: 01497186EH9 or s/n: 01919565FH9 or s/n: 01826082FH9