my e-mail address 324170455@qq.com
How can I trust that?
I have sent you my old XP image.
I have downloaded it, but I can't open it, the file seems to be bad.
Image files normally have an .iso extension.
Your file is named "hdd.iso.squashes"
Remove .squashes ( i.e change the filename to hdd.iso), and try to extract
I kept it in a SquashFS so that I could easily poke at it from linux while it was still in its compressed form. The raw hdd.iso is 78GB of zeros and 2GB of data (or something), so maintaining compression was important. I've sent you both a link to hdd.iso.zip, which should be easier to work with on windows. Unzip it and you get the full 80GB mostly empty Windows XP partition image.
Same goes for keeping it off the internet: I don't really know the rules of Windows activation, and even though I have no plans to go back to this image I'd rather it not get deactivated if possible. Thanks
Thanks, I have been using iso files without compression.
As long as I don't connect to the network, your system will not have problems.
In China, we all use pirated copies. So I can be sure that there is no problem at this point.
I tried the system you gave and reported errors.
what should I do? It costs $3000 to be sent to the official repair point.
Darn, sorry to hear. None of your options are good, unfortunately
* You could dig through the firmware folder and look for EEPROM flash tools. I only saw one for FPC (front panel control) but you have stronger motivation so maybe you will see something I missed.
* You could track down the EEPROM. If it's not buried inside a 1,000,000 ball BGA I am willing to open up my own device and give you an EEPROM image.
* You could sell your RTO1024 for parts.
* You could pay R&S the repair price
Do you have any other service code? such as 16052008f
"16052008f" and "894129" are the only two codes I know.
These are firmware, but I don't know how to burn it.
I don't know how to burn it either, sorry.
Better sell it for parts and buy something else. I'm getting the feeling there is a lot more wrong with this oscilloscope than just a firmware flash gone wrong. You shouldn't have attempted flashing the firmware before getting the scope working the way it was. Now you have two problems and you don't know how they relate to eachother.
I am more hopeful than nctnico. I still think there is hope to find & flash the EEPROMs and fix the signal integrity problem. If you do decide to sell it for parts, I would possibly be interested in buying. Is taobao the place where equipment is sold for parts in China?
Regardless, I wish you the best of luck with your efforts.
How much are you willing to pay for?
@myhobo I know at least two of us sent quotes. Hopefully no news is good news!
In any case, on my RTO1024 the vertical and horizontal scale encoders are starting to skip codes. Has anyone else had this problem? I'm trying to decide between replacing just the two encoders going bad -- which have a different mfg date and model than the others -- and replacing all of the encoders, even though they're expensive little buggers that are difficult to source.
Full details here.More importantly, the broken encoders are ones without push functionality, and it's looking like the only replacements are pushable. Will this unlock secret hidden scale fine-tuning modes?
Update: no, no it doesn't. But it's sooo nice to have working encoders again
Maybe someone here can help me. I have a RTO1022 that came with XP / 2gb RAM. The harddisk crashed. I used jjoonathan publised steps to reinstall it with Windows 7. Only things I may have done differently was that I didn't install any Windows update before running RS firmware install 3.70.1.0 and also run RS firmware install 3.70.1.0 as Administrator. It installed a lot of software and drivers and rebooted. The first time it installed some FPGA firmware and rebooted again. Next time it tries to start but gives the error below and shuts down windows (not a clean shutdown). Any Ideia of what can be wrong?
I didn't activate windows (key is good, I just didn't connected it to the Internet... always seems like a bad ideia to me). Can this be a problem?
I doubt that windows activation has anything to do with it, since we are seeing a bunch of errors that all have to do with Front End Controller communication. I have seen those particular errors before, although they never resulted in a hard reboot. They went away after the RTx.exe app successfully flashed the firmware, which did not happen until I ran RTx.exe with Administrator. You mention running the installer as Administrator, but it's not the installer that flashes the firmware, it's the RTx.exe app, the one that launches on startup and has a shortcut on the desktop (actually IIRC it's only the shortcut that is called "RTx.exe" and the actual app is "RTxLoader.exe" or something).
Have you tried running the app as Administrator?
Some tricks and tipps for you guys on RTO1000 Series:
When you have FEC / FPGA Flash error etc. on first Firmware 3.70 start, exit the application and start over RtxLoader.exe as Administrator.
Flashing should be fine than... just be patient.
8GB RAM upgrade ONLY works on BIOS 1.01
You find the Flash tool in C:/Programfiles/Rohde Schwarz/3.70.xx/Tools/BIOS
Open a comandline cmd.exe as Administrator and Flash the RTO 1.01 file located in C:/Programfiles/Rohde Schwarz/Drivers
Than be happy with 8GB RAM :-)
Thanks. I'm not with the scope now, will look later. This 1.01 is the CPU BIOS version, right? (The one we enter by pressing DEL at boot).
Thanks. I'm not with the scope now, will look later. This 1.01 is the CPU BIOS version, right? (The one we enter by pressing DEL at boot).
YES Mainboard CPU bios we are talking about
Thank you all. Fixed the scope. I entered safe mode, removed the RTx.exe from auto start, rebooted, run RTx.exe as Administrator, a few more upgrades and a reboot and it's working fine as you can see below. Just one strange nuisance remains: touchscreen mouse is upside down. When I run my finger from up to down the mouse goes up. Any more ideas?