1. the 70Mhz can be upgraded all the way to 270MHz? (or 250 safely)
In my mod I removed all Rigol licensing system - which BTW, enables some options from DHO4000 (Rigol used same code to built this firmware). So by default You have as much bandwidth as the hardware will give.
Also, You can select manually (in the channel settings - separately for each channel) AFE filters: full (usually >250 MHz unless You removed or changed LC filters between AFE and ADC), 400 MHz, 125 MHz, 100 MHz and 70 MHz.
2. the logos that appear on the screen during boot and on the interfaces can be changed or customized? is that just by you or can we modify our own logos / images?
If You unpack zip package from my mod in version 0.3 (currently only as a enterprise edition, later also as a home edition after I'll finish fixing bugs) You should have folder named custom_bootsplash. Installation script is looking for a file named image.bmp in this folder. If it exists, it's used as a system bootsplash.
In previous versions (currently v0.2.1 normal edition), script was looking for a file named custom_image1.bmp in the same directory as the installation script.
3. does no. 2 include font modifications on our end?
You can put whatever You like as a bootsplash, like a full screen image with a text only (with any font You like) or some photo or anything else.
4. it's possible to increase the memory depth of the scope beyond the 25/50 points given the physical hardware present on it?
Hardware theoretically should allow to use 268 Mpts, because FPGA DDR chip is 4 Gb (single point takes 16 bit). Likely about half of it is reserved by the FPGA firmware (AFG, LA, screen waveform points, etc), so practical (tested) limit is 134 M. Currently my mod allows You to select up to 125 M. If You are going to use more than 62.5 M in total, I strongly advice to use single shot button instead of stop button, because if You will use stop in such settings and after that You will change time base (still in stop mode instead of single shot), waveform can be disrupted.
Because of the lack of the original source code, I wasn't able to determine why this is happening. I'm planning to do a workaround by adding code to make a single shot when somebody will use stop with such memory setting.
More details about changes that I made, You can find in the
changelog for all versions from the beginning.