Interesting finding
got splashtop to spit out its convulted model name from my MB
some reason the chopped a letter off it
echo $DVM_MODEL reports M4A79XT_EVO
close enough i suppose though model number is really M479XTD_EVO
No idea what sqx files actualy contains models.d but i can view it inside splashtop in the terminal.
So i have tried my va-customres.sqx both using the board specific folder in it as well as the universal superset folder in it.
Odd thing happens, it's ignored as far as i can tell,
splashtop mounts it in /mnt/va-customres.sqx but that is about all it appears to do.
And simply mounting it is not highly useful, it doesnt actualy execute any of the files in it.
if i look at the two environment variables that should have been set by 99-custom
the values in them (in active memory) are 1024x767x40x60
and DDC=no
Incidently i found while messing with this that i can infact read and write to all my hard drives, XP, Win7, and Ubuntu.
They are all mounted in /mnt/winhdd/ (disk1, disk2, disk3 etc)
No splash apps seem to be able to navagate to anyplace beyond the USB drive, but i would guess that is the programmer just locking down the normal "look for a place to save" function
Perhaps if you changed one to be mounted in media instead, perhaps you could use it.
Havent tried yet, will try a symbolic link and see later.
At least you can go into terminal and move files or write them.
Or simply put an unsquashed script on the drive to execute for various reasons.
I tried using your little script (SPARTAN's) to change the environment variables for the resolutions.
But saddly they only exist up to the point where the python script says its now going to reload your desktop, then it seems splashtop purges memory.
It must actualy save to a file in c:\ASUS.SYS or c:\ASUS.000 to save some of the persistant settings.
so mayhaps something there is editable.
Also unsure which version of splashtop you have but the version i have here is using X, it is using the Xvesa server, not sure which WMM this thing is, i see one in the filesystem named blackbox.
Did try to run it, hehehe, of course it said display :0.0 was busy with another WMM.
So for now ive got crappy res but i do have a terminal app, pidgin, and Firefox 2.0 (3.0 fails to launch for whatever reason)
BitchX didnt work, yet.
got splashtop to spit out its convulted model name from my MB
some reason the chopped a letter off it
echo $DVM_MODEL reports M4A79XT_EVO
close enough i suppose though model number is really M479XTD_EVO
No idea what sqx files actualy contains models.d but i can view it inside splashtop in the terminal.
So i have tried my va-customres.sqx both using the board specific folder in it as well as the universal superset folder in it.
Odd thing happens, it's ignored as far as i can tell,
splashtop mounts it in /mnt/va-customres.sqx but that is about all it appears to do.
And simply mounting it is not highly useful, it doesnt actualy execute any of the files in it.
if i look at the two environment variables that should have been set by 99-custom
the values in them (in active memory) are 1024x767x40x60
and DDC=no
Incidently i found while messing with this that i can infact read and write to all my hard drives, XP, Win7, and Ubuntu.
They are all mounted in /mnt/winhdd/ (disk1, disk2, disk3 etc)
No splash apps seem to be able to navagate to anyplace beyond the USB drive, but i would guess that is the programmer just locking down the normal "look for a place to save" function
Perhaps if you changed one to be mounted in media instead, perhaps you could use it.
Havent tried yet, will try a symbolic link and see later.
At least you can go into terminal and move files or write them.
Or simply put an unsquashed script on the drive to execute for various reasons.
I tried using your little script (SPARTAN's) to change the environment variables for the resolutions.
But saddly they only exist up to the point where the python script says its now going to reload your desktop, then it seems splashtop purges memory.
It must actualy save to a file in c:\ASUS.SYS or c:\ASUS.000 to save some of the persistant settings.
so mayhaps something there is editable.
Also unsure which version of splashtop you have but the version i have here is using X, it is using the Xvesa server, not sure which WMM this thing is, i see one in the filesystem named blackbox.
Did try to run it, hehehe, of course it said display :0.0 was busy with another WMM.
So for now ive got crappy res but i do have a terminal app, pidgin, and Firefox 2.0 (3.0 fails to launch for whatever reason)
BitchX didnt work, yet.
Comment