So I did the update to 2.37 and tried how to downgrad to V2.35.
The first step was a modified cab based on V2.35 and Infiniivision.cab from 2.37 to change the Windows folder with the ProcessStartupFolder.exe
The 2.37 Firmware has loaded the Firmware Update successfully but it takes a couple of minutes before the scope reboots.
This is the simples way to restore the \windows folder to an older version because ist write protected.
The next Step was to rename the 2.37 to 2.35 in the infiniiVisionLauncher and infiniiVisionCore and replaced these files directly over telnet from usb to the \sercure folder.
after a reboot i tried to load a V2.35 Firmware but this didn't works maybe the timestamp was also checked.
After I replaced the newest files in the \secure\infiniivision folder direcly with the 2.35 Files I was able to load the old v2.35 setup.
So its posible to go back to the V2.35 with the help of telnet access.
Been for a walk on the beach and I've come back this this with a clear head...
I've done the following:
1) Taken the 2.35 CAB file and extracted the infiniiVisionSetup.cab file
2) Upacked the 2.37 CAB file and replaced its infiniiVisionSetup.cab file with the one I extracted above
3) Used a program called CABPACK to create a new hybrid CAB file from the unpacked 2.37 with its new 2.35 component
The intention is to put this on a USB stick and then do a firmware upgrade, hopefully this is the same thing kilobyte did in the first part of the process he describes above.
I'm a little reluctant to try this, mainly because my new hybrid CAB file is 19 meg in size and the original 2.35 and 2.37 CAB files were 22 meg!!
Might have to have a bottle of vodka to hand before I push the button on this...