I've never really installed a beta before and thats maybe why...

Files like Chicago 224 ISO (from SillyProject) need a boot disk apparently? And by the looks of the contents theres no setup.exe inside the Chicago ISO..? Is that normal?

Could anyone possibly help me with how to install these, I'm lost.

As for the boot disk, a standard Win95 or 98 (with CD drivers) should work. A setup.exe (or install.exe) should be somewhere in the image.

There is no setup.exe present and a few files named setup in the cab files but no setup.EXE and there is no mini.cab and no precopy1.cab

So its not installable, these files are missing.

dont forget that windows95/chicago and win98/memphis will not boot if your cpu is larger than 2.1 gigajertz ( although you should be able to apply the win98 large cpu patch from dos using a bootdisk) and that win95a and chicago need a drive that is formatted as fat16 not fat32. *i dont know why there wouldnt be a setup.exe or a mini.cab, it sounds like its a incomplete copy?

Maybe you can take these files from Chicago Build 225:
Dossetup.bin
Winsetup.bin
Xmsmmgr.exe
Setup.exe
Precopy1.cab

And add them to your copy of Chicago Build 224.

The file on SillyProject and Abyssunderground (HD 2) that contains Chicago Build 225 is named "Windows 95 Beta 1.rar".

I've never heard of that limitation nor that patch.

Neither am I why am I running a version of Chicago beta build 73 in VPC now then?

build 58 and 73 probably work differently to windows 95, if you want to see if im right, install win95 or 98 on a harddrive, then connect that drive to a pc that has a cpu larger than 2.1 gighertz, i.ll bet my left nut you will get a error as soon as windows boots. fyi : windows me is ok because it supports up to a 5 gighertz cpu.

I know you're right, Iv'e seen & posted the MS page that stated this as a
fact when OSBA was up...
I'll google for it later & post it here seeing others are too lazy to look for
themselves...

at the boottom of the page where it asks "did this help fix your problem" i ticked NO and posted this in the feedback box - microsoft should support windows 98 and windows 95 or declare them to be abandonware.

This error seems very random - I had a Windows 95 Virtual PC that worked fine on my old 3.4 GHz P4HT laptop, but didn't work (because of this error) on my new 2.66 GHz C2D (which actually seems to only run at 2.14 GHz although Windows identifies it as a 2.66 GHz chip, because of some weirdness that I can't figure out, to do with the board being supposed to be capable of 1333 MHz FSB but in fact automatically disabling the setting to get that FSB when I try to enable it, and the CPU speed being a multiplier of that, but that's another story for another day...), but Windows 95 in VMware and Windows 98 in Virtual PC work fine on my new system, and 98 in VPC also worked fine on the old one.

It is because your CPU is supposed to run at FSB1333 and the 945 chipset on your board maxes out at FSB1066, FSB1333 is only "officially" supported on 965 chipsets and up. As the 8.0 multiplier is hard-coded (increasing is not possible, decreasing is), the clock speed directly depends on the FSB.

Yep, I get that bit, the bit I don't get is why when I set the "enable 1333 MHz FSB overclock" setting that is in the Bios and documented in the manual, it just restarts and has disabled that setting again

Typically, when I 1st posted that MS link 2 or more years ago, 98se was
still supported, yet they said then that there was no workaround as of yet...
Now of course the page has since been updated & their using the excuse that the
OS is no longer supported, ""They say - as they wipe thier hands of it""

yeah typicall Ms! i just uploaded the windows 98 patch if anyone wants it ( there is a bootdisk version but i cant find it) http://rapidshare.com/files/78014362/2GIGCPU.zip