« previous next »
Pages: 1 2 [3]   Go Down

Author Topic: OS 1.03 and PHYSIUM add-in  (Read 16976 times)

0 Members and 1 Guest are viewing this topic.

Offline Darl181

  • «Yo buddy, you still alive?»
  • CoT Emeritus
  • LV12 Extreme Poster (Next: 5000)
  • *
  • Posts: 3408
  • Rating: +305/-13
  • VGhlIEdhbWU=
    • View Profile
    • darl181.webuda.com
Re: OS 1.03 and PHYSIUM add-in
« Reply #30 on: October 23, 2011, 05:33:25 pm »
Quote from: JosJuice on October 23, 2011, 01:56:04 pm
Quote from: alberthrocks on October 23, 2011, 12:10:45 pm
* alberthrocks pokes Casio to make a TI-Connect, but 1000x better :P
They have made a linking program for their calcs, but the Prizm doesn't use it since MSD mode is so much better.
Hmm..
I'm guessing the Prizm can handle as a host in the USB connection, what with the data-collecting tools and such.  Would a program to use a flash drive be possible?  I'm not talking about now, but at some point in the future when we know more about the USB port or something...
« Last Edit: October 23, 2011, 07:37:21 pm by Darl181 »
Logged
Vy'o'us pleorsdti thl'e gjaemue

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: OS 1.03 and PHYSIUM add-in
« Reply #31 on: October 24, 2011, 02:00:25 am »
Quote from: Darl181 on October 23, 2011, 05:33:25 pm
Quote from: JosJuice on October 23, 2011, 01:56:04 pm
Quote from: alberthrocks on October 23, 2011, 12:10:45 pm
* alberthrocks pokes Casio to make a TI-Connect, but 1000x better :P
They have made a linking program for their calcs, but the Prizm doesn't use it since MSD mode is so much better.
Hmm..
I'm guessing the Prizm can handle as a host in the USB connection, what with the data-collecting tools and such.  Would a program to use a flash drive be possible?  I'm not talking about now, but at some point in the future when we know more about the USB port or something...
No, the Prizm is incapable of acting as a host. Mini-A cables won't even fit into the calc. I think data collection is done using the serial link.
Logged

Offline TIfanx1999

  • ಠ_ಠ ( ͡° ͜ʖ ͡°)
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 6173
  • Rating: +191/-9
    • View Profile
Re: OS 1.03 and PHYSIUM add-in
« Reply #32 on: October 24, 2011, 02:52:30 am »
This is really nice. It's good to see a developer actually fixing bugs reported by users in a timely manner. =)
Logged

Offline MPoupe

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 168
  • Rating: +30/-1
  • The coder of yesterday
    • View Profile
    • My web site about Casio calculator
Re: OS 1.03 and PHYSIUM add-in
« Reply #33 on: October 24, 2011, 11:29:31 am »
The Physium add-in is very big, I think it is not copied to the RAM but the corresponding flash part is mapped to the address where add-in should start. But what happens, if the physium (or other larger file add-in) becomes fragmented ?
Logged

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: OS 1.03 and PHYSIUM add-in
« Reply #34 on: October 24, 2011, 11:00:01 pm »
Because Casio removed the 1 Mb limit that would mean that the code used to manage the mmu (virtual memory) has been changed. Previously the executable contents of the g3a file were mapped to virtual memory in pages of a size of 64 kb (I believe) with the mmu capable of holding up to only 128 pages at a time which would mean that the max executable size of a g3a could be 1 Mb . Pages themselves for the sh4a can vary from 1 kb to 1 Mb. Now with the OS update it seems as if the new code uses larger pages (to be checked later once I download this). This also means that more space in the mmu table is available so other programs will have more flexibility if they rely on virtual memory. And also it is not an issue if programs are fragmented as they are mapped as multiple pages but I've never seen this before with the memory and if there wasn't enough room for a file the OS will just run garbage collecting to open up a large enough gap. My last remark is that apps are never loaded to ram for execution but are instead kept in flash. Due to the technical nature of the sh4a reading from flash and ram takes exactly the same amount of time, it is only writing that is done differently. Also for the majority of the time most reads and writes are done in the cache which is significantly faster.

Edit: btw with the physium add-in I can recall some discussion awhile back on the Casio education fb page asking for an app with a periodic table. Perhaps Casio has fully entered the social media world and is taking suggestions from there?
« Last Edit: October 25, 2011, 12:20:53 am by z80man »
Logged
+1/-0 karm for this message

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline bsl

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 157
  • Rating: +14/-0
    • View Profile
Re: OS 1.03 and PHYSIUM add-in
« Reply #35 on: November 01, 2011, 01:05:17 am »
Quote from: JosJuice on October 23, 2011, 05:07:30 am
Quote from: alberthrocks on October 22, 2011, 05:22:36 pm
It seems CASIO isn't too open about how to update their OS.... their update process is encoded inside the MSI! O_O
The update process does not extract any useful files, and the updating is done inside the MSI.

(InstallShield self-extracting EXE -> InstallShield MSI -> OS Updater inside MSI)

I've dumped the MSI's contents for those who want to try to find a solution.
http://dl.dropbox.com/u/1016340/MSIDump.zip
In OS 1.02, I believe that the OS was contained within the OSupdateDLL.dll file, and a program was written to extract it. Is this DLL file still present? I haven't been able to look at the 1.03 MSI yet.
I think  that program has to be rewritten , here are the resources I found in that dll:
3841
3842
3843
3857
3858
3859
3860
3865
3866
3867
3868
3869
3887
Logged
Pages: 1 2 [3]   Go Up
« previous next »