It's just this one unit, there must be something wrong with it. But I only have/had this one F520 model so cannot rule out a model issue. My other CRTs do not have/had this issue.Thanks for the write up. I'm wondering why people are having problems with WPB now. I don't remember anyone having these issues a few years back. The successful ones I did were all on Windows 7. Had some issues with it on Windows 10 so I decided to abort instead of fiddling around with it when I did try it a year or so ago. I assume you're on Windows 10 right? (Though I have an FW900, sounds like the same problems are popping up with the newer chassis too.)
That would be very interesting to have but Windas must be the only version that was cracked and made its way online. I think the software originally required a dongle plugged on a (serial ?) port of the computer to work.edit: By the way, IIRC WinDAS is based on DOS program called DAS or Sony DAS, does anyone still have the files and can share it?
Thank you for this share. I am pleased to have found a probable solution to my question back on page 379. In DAS_Monitor-select.jpg, I added the model to ZMODEL.DB using xDBD and then selected it in DAS. The STP file on the right proves that it should be supported. I doubt I edited all fields accurately. Attempting to save the EEPROM from the monitor failed, giving the database error in DAS_EEPROM_save-error-crop.jpg. I believe it is caused by my faulty configuration. The step by step alignment process menu was available -- the relevant sequences were listed for the correct model. Prior to editing the database I had tried to load the model of the Sony equivalent of this monitor's chassis, the GDM-20SE2T which was a bad idea and blue screened the computer -- the monitor's OSD was locked on reboot -- a predictable outcome of an interrupted alignment. "Final Adjustment" worked to restore access to it. None of the alignment procedures worked, as seen in DAS_alignment-fail-crop.jpg. Note that the horizontal and vertical timing is accurately reported in the midst of this failure. From this I conclude the software is communicating properly with the monitor. For completeness I include DAS_failure_information_Prime-crop.jpg where the rates for 1280x1024 85 Hz are reported.Sony DAS (Digital Alignment System) for DOS (v4.2.1, 2/05/98) EXE Program Download
Another user tells me:
"Now, there is one problem. You have to add all of the
rest of the monitors in the STP files to the ZModels.db file with the
correct monitor model N2H, X1, etc. using dBase3 or Borland's Paradox or
the program won't see them. I added all of the Sun, SGI models I work on
and DAS finds them correctly now."
Ah I forgot to type that my 375 is at 2235 x 1397. I updated my reply. A different resolution might be higher, but at 500+? Wow. My Delock, which is the same as the Sunix as far as I am aware, also couldn't make it past 375 at my funky resolution and a few other resolutions.
Yep that is the one. It's the Delock 87685 which has the 1 x DisplayPort 20, 1 x HDMI,and 1 x VGA output. This one.Does you Delock have a single DP, HDMI, and VGA output? Because that's the one that is the same as the Sunix. And yeah, I've tested my Sunix up to near 550mHz.
My Delock 87685 was able to go up to a measured 539MHz using the Nvidia Control Panel and CRU as a measurement of Pixel Clock, it would not display any image if i went up to 540MHz sadly. I have pics if yall need them.
Another one down.Today. I turned my fw900 on, it had a long sizzle and some flash on the front of the screen. Then I tried to turn it on again, and I heard a pop. Now whenever I turn it on it tries to turn on the lamp but there's just an electric sound again and again and nothing works. I will open it tommorow to see what broke exactly... although, does anyone know where I could send it for repair ?