[OFFER]: Windows 98 build 1611

[captainlinux8880]

It was posted on 86Box Discord server by Overdoze. There are 14 CAB files missing in this release, but they can be replaced from build 1602 or 1614.

Missing files:

• WIN98_59.CAB

• WIN98_60.CAB

• WIN98_61.CAB

• WIN98_62.CAB

• WIN98_63.CAB

• WIN98_64.CAB

• WIN98_65.CAB

• WIN98_66.CAB

• WIN98_67.CAB

• WIN98_68.CAB

• WIN98_69.CAB

• WIN98_70.CAB

• WIN98_71.CAB

• WIN98_72.CAB

Download: https://mega.nz/file/CgpGRQKA#GnZPcFSbt ... 9Q7i9Pmnvo

[MyFaceNeverWhen]

This is as far as I got using CAB files from 1614:



Has anyone got this working yet?

[captainlinux8880]

This is as far as I got using CAB files from 1614:



Has anyone got this working yet?

Yeah, I compiled the ISO from the available archives, and also read the information on the BetaWorld Wiki and 86Box Discord server. It is claimed that 14 CAB files are missing after win98_58.cab. BetaWorld users were able to get it to work. https://wiki.betaworld.cn/Windows_98:4.1.1611

However, for me and for you, the installer successfully reads win98_59.cab, but then refuses.

But what if you try to put the requested files on another ISO?

[MyFaceNeverWhen]

This is as far as I got using CAB files from 1614:



Has anyone got this working yet?

Yeah, I compiled the ISO from the available archives, and also read the information on the BetaWorld Wiki and 86Box Discord server. It is claimed that 14 CAB files are missing after win98_58.cab. BetaWorld users were able to get it to work. https://wiki.betaworld.cn/Windows_98:4.1.1611

However, for me and for you, the installer successfully reads win98_59.cab, but then refuses.

But what if you try to put the requested files on another ISO?

It does work that way. You just have to occasionally switch directories or skip files.

[captainlinux8880]

Yeah, I compiled the ISO from the available archives, and also read the information on the BetaWorld Wiki and 86Box Discord server. It is claimed that 14 CAB files are missing after win98_58.cab. BetaWorld users were able to get it to work. https://wiki.betaworld.cn/Windows_98:4.1.1611

However, for me and for you, the installer successfully reads win98_59.cab, but then refuses.

But what if you try to put the requested files on another ISO?

It does work that way. You just have to occasionally switch directories or skip files.

[DiskingRound]

If it was a warez dump, it is very likely that the missing CABs are a result of corruption. The other day I found Windows 95 build 346 on a warez CD, but half the build was corrupted.

[captainlinux8880]

If it was a warez dump, it is very likely that the missing CABs are a result of corruption. The other day I found Windows 95 build 346 on a warez CD, but half the build was corrupted.

yeah, this is a very common occurrence. I was reminded of the case with Windows NT 3.5 build 683 Workstation SKU, when by mistake 1.68 MB floppy disks were dumped into 1.44 MB, and thus ruined the entire release.

[mrpijey]

Could we pack up, document and archive these incomplete releases? Then we can save whatever exists and use it as reference in case the full stuff comes along in the future.

[MyFaceNeverWhen]

Could we pack up, document and archive these incomplete releases? Then we can save whatever exists and use it as reference in case the full stuff comes along in the future.

Fine with me.

[anonymous74]

yeah, I'd say archive it. It doesn't hurt.

[captainlinux8880]

Could we pack up, document and archive these incomplete releases? Then we can save whatever exists and use it as reference in case the full stuff comes along in the future.

FTP has an "Incompletes" section, so I don't see a problem.

[mrpijey]

I know that, I created the incomplete section . My point is, can someone help pack up, document and upload these incompletes so we can add them?

[captainlinux8880]

I know that, I created the incomplete section . My point is, can someone help pack up, document and upload these incompletes so we can add them?

Ah... I misunderstood your post a bit

[captainlinux8880]

Could we pack up, document and archive these incomplete releases? Then we can save whatever exists and use it as reference in case the full stuff comes along in the future.

I documented the release and uploaded it to FTP.