This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Jim Bauwens
Pages: 1 ... 80 81 [82] 83 84 ... 125
1216
« on: October 02, 2011, 11:02:27 am »
I think we should keep a copy of this buggy OmnomIRC and give it to Mozilla. It is the web dev's fault in this case, but it might be interesting for them to analyze. Their memory profiling is top notch, and this case scenario might enable them to optimize more...
I don't think they are interested, because I submitted a bug report of a script that fills the entire memory in seconds, and they didn't care.
1217
« on: October 01, 2011, 04:55:42 pm »
Very nice! Will try to try it when I get some time 
1218
« on: October 01, 2011, 01:28:06 pm »
I'm terribly sorry, totally forgot about this!
I think the easiest would be to use a smaller font, because I only find a few characters, not all of them.
1219
« on: October 01, 2011, 06:43:19 am »
Alrighty, I managed to extract an ext2 image out of it:
dd if=initrd.e2fs.gz.uboot bs=1 skip=64 of=rootfs.ext2.gz
gzip -d rootfs.ext2.gz
I need to use to split the file because the first part is a uImage (kernel) header.
Now you have the ext2 image, simple mount it (sudo mount -o loop rootfs.ext2 /path/to/mount/point).
In it you can see that it uses the RADIUS technology for its network. Also, it looks like it contains a SSH server, so you should be able to SSH into it.
Here are the file results on initrd.e2fs.gz.uboot and uImage:
uImage: u-boot legacy uImage, Linux-2.6.31.13, Linux/ARM, OS Kernel Image (Not compressed), 1655392 bytes, Wed Jan 19 19:11:06 2011, Load Address: 0x80008000, Entry Point: 0x80008000, Header CRC: 0x5D8D20F3, Data CRC: 0xCB86419D
initrd.e2fs.gz.uboot: u-boot legacy uImage, NWB Image 3.0.0.20, Linux/ARM, RAMDisk Image (gzip), 4937853 bytes, Wed Jan 19 19:11:44 2011, Load Address: 0x81000000, Entry Point: 0x81000000, Header CRC: 0xA0DE5B4D, Data CRC: 0x0D85D138
1220
« on: October 01, 2011, 04:37:51 am »
To get OS >3 running in the emulator, you need an older boot2 (like 1.4.0). Download an older OS, and open it with winrar or 7zip. Extract the boot2 image. Then you need to use imagedump.exe to decompress the boot2. So, in the end you need the boot2 from an earlier version, and TI-Nspire.img from the OS 3. Then just follow the normal instructions I guess
1221
« on: September 30, 2011, 05:55:27 pm »
Hah, so Linux anyway! Will check it out tomorrow, to see if I can get some interesting bits out of it 
1222
« on: September 30, 2011, 03:38:27 pm »
Interesting information! Would love to get my hands on one to test stuff with 
1223
« on: September 28, 2011, 02:16:49 pm »
*jimbauwens hugs his brother
1224
« on: September 28, 2011, 02:09:45 pm »
Awesome.
1225
« on: September 26, 2011, 06:14:33 pm »
I'd love to do it, but sometimes I really don't have time during the day. Currently I need to do lots of studying, and will be less active the next weeks, so idk 
1226
« on: September 24, 2011, 05:17:59 pm »
Very cool!
1227
« on: September 24, 2011, 05:09:43 pm »
Hmm, probably. Thanks for noting, didn't think about it @Frog, I don't know immediately, will check tomorrow.
1228
« on: September 24, 2011, 11:36:10 am »
Looks very nice, good job
1229
« on: September 24, 2011, 05:35:33 am »
No problem, glad I could be a help
1230
« on: September 23, 2011, 03:43:06 pm »
Well, string.byte looks at the string as if it would be ascii, but in fact the nspire uses utf-8. UTF-8 uses multiple bytes, unlike ascii. And since string.byte is for ascii, it takes only the first byte, 194.
To make a story short, you need string.char(194, 178) for ². 194 is the first byte, 178 the second.
Now, to find the bytes of a utf-8 char first use string.len, to see how many bytes there are. Then use string.byte to fetch the chars:
ch="²"
string.len(ch) --returns 2
b1=ch:byte(1) --returns 194
b2=ch:byte(2) -- returns 178
chr = string.byte(194, 178) --returns ²
Pages: 1 ... 80 81 [82] 83 84 ... 125
|
Show Posts