[Offer] Microsoft Windows 1.0x (End user or Developer)
Windows 1.01 is exist on this link
https://winworldpc.com/download/417EB4E ... 54D21A8599
Unfortunately, this is Not dumped from original disks as Floppy Disk Image.
(The reason : 1.Boot Sector is strange 2. Non used sector is also different from original. 3. A few of directory (PIF) is excluded.)
I got copied disk of 1.01 a few years ago, but I could't confirm that is same as original.
But thanks to other Abandonware site's user contribution I can verify it.
Now I uploaded correct Windows 1.01 dumped from original disk.
This is information of SHA1.
(Unfortunately my original disk was lost a few years ago, only remained as Floppy Image from back-up disks. So I can't attach scan image of each disk label.)
SHA1:7075bfa3af2a18d3d680d779630aace7e31f5bf9 / DISK1-SETUP.IMG
SHA1:d783941a437b942a7796556702dd2c584c8a3487 / DISK2-BUILD.IMG
SHA1:d239d74ab3a082c5129bb6237b58e5a5b0d5fd81 / DISK3-UTILITY.IMG
SHA1:d77c4991f31875572ca0dd9226c81202b3b63bab / DISK4-APPS.IMG
SHA1:c964feed584a52b52c431d03308b960f36543f20 / DISK5-WRITE.IMG
Floppy Disk Image is uploaded on ftp.
https://winworldpc.com/download/417EB4E ... 54D21A8599
Unfortunately, this is Not dumped from original disks as Floppy Disk Image.
(The reason : 1.Boot Sector is strange 2. Non used sector is also different from original. 3. A few of directory (PIF) is excluded.)
I got copied disk of 1.01 a few years ago, but I could't confirm that is same as original.
But thanks to other Abandonware site's user contribution I can verify it.
Now I uploaded correct Windows 1.01 dumped from original disk.
This is information of SHA1.
(Unfortunately my original disk was lost a few years ago, only remained as Floppy Image from back-up disks. So I can't attach scan image of each disk label.)
SHA1:7075bfa3af2a18d3d680d779630aace7e31f5bf9 / DISK1-SETUP.IMG
SHA1:d783941a437b942a7796556702dd2c584c8a3487 / DISK2-BUILD.IMG
SHA1:d239d74ab3a082c5129bb6237b58e5a5b0d5fd81 / DISK3-UTILITY.IMG
SHA1:d77c4991f31875572ca0dd9226c81202b3b63bab / DISK4-APPS.IMG
SHA1:c964feed584a52b52c431d03308b960f36543f20 / DISK5-WRITE.IMG
Floppy Disk Image is uploaded on ftp.
Comments
Windows 1.03 exists on this link
https://winworldpc.com/download/41930F5 ... 54D21A8599
Unfortunately, that is Not dumped from original disks as Floppy Disk Image.
(The reason : 1.Boot Sector is strange 2. Non used sector is also different from original. 3. A few of directory (PIF) is excluded.)
Attached content : 7 Disk Image (5.25" 360KB) / 6 Diskette Art
(SHA1 Information)
SHA1:97a1824ecb76cbaa60a0b3830fcdcd2a0682dfc8 / DISK1.IMA
SHA1:67f4fa933b7747454d5539951f17a11eeb7862e7 / DISK2.IMA
SHA1:d8e9459afa5d2fac2b97e4b828b406f5907084fa / DISK2A.IMA
SHA1:3ac982e78e4add5db22e070f2d32dcd2089563c6 / DISK3.IMA
SHA1:b82fa8b4a4ec6828d5cf64bea98d5d2b7c09b7a7 / DISK4.IMA
SHA1:77a97d10925401a7980379a26d831d1a062397c5 / DISK5.IMA
SHA1:7fc7f45aac4f896dbbe1f8a7bf0f95273fa2c7d4 / DISK6.IMA --> Write Program Disk
The difference between DISK2.IMA and DISK2A.IMA are related with version of USER.EXE.
I figured out that they exist as 2 versions on Disk 2.
(Of course I've compared Disk 2 with other user's ones and they're verified.)
DISK2.IMA --> USER.EXE (122,416) (05-22-1986, 03:49:52)
DISK2A.IMA --> USER.EXE (122,432) (08-24-1986, 15:57:02)
The difference between DISK2.IMA and DISK2A.IMA is related with USER.EXE.
DISK2.IMA <-- Original release 1.03
DISK2A.IMA <-- Updated release 1.03
*Difference Offset Range : 00000A76 ~ 00000A7C / 00018802 ~ 000367FF
Except Disk 2, No difference has found on Disk 1 / Disk 3-6 (Disk 6 is called as Write Program Disk)
My dumped retail disk 2 is same as DISK2A.IMA.
Before I've got l disk, I used to have copied disk of Windows 1.03. (Disk 2 is just same as DISK2.IMA but I did't know disk is verified.)
Now they're verified.
Original release version 1.03 is already downloadable on ftp from 2 years ago.
--> Also Tandon OEM 1.03 version is just same.
Updated release version 1.03 was dumped by any abandonware site about 9 month ago.
--> I've also downloaded and checked it but Disk 1 has still bad dumed. (Error on Track 1 / Side 0 / Sector 1-9)
I bought retail diskette about 3 months ago and dumped it.
Oops, I must rename the DISK2.JPG as DISK2A.JPG.
If the DISK2.IMA and DISK2A.IMA are confused to contribue (upload), I'll re-upload it.
So what you are saying is that both are authentic. And your disk set and another one match DISK2A. But other known good copies match DISK2 (and are otherwise identical).
Looking closer, it looks like Microsoft slipped some tiny code update in to the user.exe.
I take it there is nothing on the disk labels or packaging to indicate the difference?
Ok, thanks.
>>So what you are saying is that both are authentic. And your disk set and another one match DISK2A. But other known good copies match DISK2 (and are otherwise identical).
That's right!
>>Looking closer, it looks like Microsoft slipped some tiny code update in to the user.exe.
>>I take it there is nothing on the disk labels or packaging to indicate the difference?
At least DISK2A.IMA is from Microsoft Retail disk, this is true. (I verified it with disk labels due to another abandonware site.)
I can't say DISK2.IMA is from Microsoft Retail disk definitely, but it is verified that is also authentic which is compared with Tandon OEM or other modified disk image.
Can you rename DISK2.IMA --> DISK2O.IMA and DISK2A.IMA --> DISK2.IMA?
This must be best way not to be confused.
DISK2O.IMA means it is from OEM at least.
Microsoft Windows 1.03 (08-21-86) (5.25)
and
Microsoft Windows 1.03 (08-24-86) (5.25)
The dates are based off of the newest file date in each set.
And added some information about these to the 1.03 release description.
Thanks for contributing to Winworld, your primary source of rutabagas and laminated cardstock.
Ok, thanks.
* Windows 1.03 was also dumped from another abandonware site before I got this on Sep 2014. (Dated : 03-29-2014)
I've checked it with mines.
Unfortunately Disk 1 is broken (bad dumped) on another's one.
(Of course my dumped one is no error and good dumped.)
If anyone found "SHA1:5ad3f4dcc3fedabd21000d4c639de3a961c9f37f" of Disk 1 (Disk01.img), that is broken obviously.
Broken area : Track 1 / Side 0 / Sector 1-9, All contents are filled as 00h. (In other words, the dumped area was skipped or ignored due to disk error or other reason.)
SHA1:5ad3f4dcc3fedabd21000d4c639de3a961c9f37f <-- dumped incompletely on Track 1/0/1-9 (Offset : 0000:2400 - 0000:35FF) (Broken FIle : SETUP.EXE)
SHA1:97a1824ecb76cbaa60a0b3830fcdcd2a0682dfc8 <--- dumped correctly and perfectly
*Microsoft Windows 1.0 Premiere Edition
Attached content : 4 Disk Image (5.25" 360KB)
SHA1:798bd4b246fb0dd473b9f30d3398e128f10b799c / DISK1.IMA
SHA1:f392dae5c6329d103ba837a9098f1c5fadf6797d / DISK2.IMA
SHA1:e59b26fd276fab079bf845e5d704827cc54ffe50 / DISK3.IMA
SHA1:0322a886820c133438bcc7d0c7df80e5bdda8f82 / DISK4.IMA
(This is Not mine! but I verified!)
*Microsoft Windows 1.04 (5.25")
Attached content : 7 Disk Image (5.25" 360KB)
SHA1:af1846492ceda98b80507940dedc8e8312c04c5b / DISK1.IMG
SHA1:4052d4cab6aece95e8cb61f02ceedb2424c4a61b / DISK2.IMG
SHA1:a482648122ee6f45fa4daa3c85f6d490b08c3cb1 / DISK3.IMG
SHA1:fe614d9b031bee04c518702035fba20d3e29c0c7 / DISK4.IMG
SHA1:ff95c2c5ca2d28d168e6ecebbd00e919be0f8c29 / DISK5.IMG
SHA1:729c4ea69708654c53c3c9c3a2e0b4ee5f04c1b9 / DISK6.IMG
SHA1:40e0ebcec1f830afec6303d2825f520f41355dfc / DISK7.IMG
*Microsoft Windows SDK 1.04 (5.25")
Attached content : 7 Disk Image (5.25" 360KB)
SHA1:8bd638f9ea3cb531beca0cf8642a840fefcea4fe / DISK1.IMG
SHA1:d82829f6ac312080ec55df75c449a3a092e1d6e3 / DISK2.IMG
SHA1:e7719dc88c47ab135c605a2e81132e4e05e9d788 / DISK3.IMG
SHA1:60155ff14fc8facbd8877d73606b03a5f219c38a / DISK4.IMG
SHA1:16d86981b625ca61b90a2f8bfa0e2ddbb8a673a1 / DISK5.IMG
SHA1:4c3690cbce4e3732c25e3b02627cb0d1feac745f / DISK6.IMG
SHA1:03d3afb810a0816ca561b228aa1f1c0fa85edd77 / DISK7.IMG
*Already uploaded Microsoft Windows SDK 1.03 must be dumped correctly.
Now except Windows 1.02, all of 1.01 / 1.03 / 1.04 are dumped from original disks.
I recommend to change attribute of File Archive for "Microsoft Windows SDK version 1.03" as 5.25 Floppy
Well, we still need the 720k IBM OEM Windows 1.04
Thanks for contributing these!
I hope so.
This must be rare 3.5" version of Windows 1.0x
Logically this version should therefore also include PS/2 mouse support. That would certainly explain why some accounts of 1.04 say it supports PS/2 mice.
Windows 1.02 was dumped from original disk by the user "RubyTuesday" on BA.
Disk 5 and Disk 6 include bad dumped area, but the sector area is non allocated with Windows file, unused. I fixed the bad dumped area perfectly.)
*Microsoft Windows 1.02 (5.25")
Attached content : 6 Disk Images (5.25" 360KB)
SHA1:c80d053ad34c49c6fa07be018c49271d4f87f1a8 / DISK01
SHA1:274b531a474cf82c5018c52553f32457f956023a / DISK02
SHA1:e91009a2812a877e835d787c66cfcd289e5f3d64 / DISK03
SHA1:badef9256878317b87c44900c767de7f2b6183ee / DISK04
SHA1:20e82e8128cb3b2ba5f4458b9cf947b39dc4fb2f / DISK05
SHA1:7a5171c160e8b5f9b493d019b8fe47e23ce937bc / DISK06
Also I uploaded minor updated version of Windows 1.03 (5.25")
*Microsoft Windows 1.04 (5.25") (05-11-1987)
Attached content : 2 Disk Images (5.25" 360KB)
SHA1:ed37cff589928c1d386f31d04ee0bbb7f9ed741c / DISK05 (Application)
SHA1:8925edbc5f1a27078967cc21c9c3c9fd652450ac / DISK06 (Write)
I didn't attach Disk01~Disk04 / Disk07, because they're same as already uploaded one.
https://winworldpc.com/download/4E7B2E4 ... 04A6F17893
I recommend to rename uploaded Windows 1.04 as Windows 1.04 (04-10-1987).
Windows 1.04 (05-11-1987) includes 7ea of 5.25" 360KB, but Disk 1-4 / Disk 7 are same as Windows 1.04 (04-10-1987).
Only Disk 5 and 6 are minor updated.
Attached content : 8 Disk Images (5.25" 360KB)
SHA1:e7ce0b528117b54e84845a6657e452504190b4da / DISK01 (Utilities)
SHA1:c70bb6f7669c8dd4c3c769c6c4a3872480807033 / DISK02 (LIB Small)
SHA1:c7627a3a621afb4fd111ce161cafe88e5be30dd3 / DISK03 (LIB Medium)
SHA1:fe1d6c5dbf97c93b44103640da1a4d30a5d9e728 / DISK04 (LIB Large)
SHA1:d3696123a87d8af0b6a912cb164a7c884a7390ef / DISK05 (LIB Pascal)
SHA1:85a64b61f62bbd01ec07dd729916af3ab5495902 / DISK06 (INC Pic)
SHA1:abc87369fd3c3a438fe97cf26384a19f7451e861 / DISK07 (Samples)
SHA1:40b407dbaadb3abce6ddf893bcda2938e0d12c96 / C-UPDATE (C Update)
*Microsoft Windows Runtime 1.01 (5.25") for developer
Attached content : 4 Disk Images (5.25" 360KB)
SHA1:a987436e04ff0d622f432b20f90bc42ca04e5c2f / DISK01 (Setup)
SHA1:5acff47f3de15c204241d04b02548fe8b7ba0459 / DISK02 (Build)
SHA1:bfb832cbeab22e9f0f97bc2d1736e335acdc09c3 / DISK03 (Utility)
SHA1:23dbdf2777cd664a4d06a9451204033409ebb759 / DISK04 (Application)
DISK07 is modified (Written) MAKEFILE (1986) on "C" directory.
Thanks to any Ebay seller, I can fix (restore) the problem.
So I uploaded DISK07 (Samples) again.
SHA1:a2ef5bcf2416c0a9679b814a57659eb80ac128b4 / DISK07 (Samples)
Also this can be downloaded from the URL
https://mega.co.nz/#!2lFEwCiT!WpaqX-55b ... ooO_xJQ18U
I figured out that leaked image fromAlias is modified on Disk 4.
(Modified)
SHA1:0322a886820c133438bcc7d0c7df80e5bdda8f82 / DISK4.IMA
(Untouched)
SHA1:1eb017daad451c907f920d1e52523a043413155c / DISK04.IMG