Omnimaga

Omnimaga => News => Topic started by: fxdev on October 21, 2011, 09:05:51 am

Title: OS 1.03 and PHYSIUM add-in
Post by: fxdev on October 21, 2011, 09:05:51 am: Download: https://edu.casio.com

Fixed issues / Bugs that I reported:
- locate bug (Glitch with multibyte characters)
- RclCapt bug (Severe memory corruption)
- Exp>Str() bug (System error)
- Solve/SolveN bugs (System error or freeze)
- 'Colons within text' bug (Long-standing Casio-Basic bug)
- Capture bitmap bug (Vertical black line on the right)
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Eiyeron on October 21, 2011, 12:32:42 pm: Yihaaaw! Locate bug fixed!
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 21, 2011, 12:40:34 pm: It's wonderful to know that Casio are listening to us and fixing the bugs. It truly feels like they care about everything, and that's great!
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Eiyeron on October 21, 2011, 12:42:48 pm: And they make these fixes FAST, and that's too great!
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: turiqwalrus on October 21, 2011, 01:06:35 pm: Quote from: JosJuice on October 21, 2011, 12:40:34 pm
It's wonderful to know that Casio are listening to us and fixing the bugs. It truly feels like they care about everything, and that's great!
which is one thing that we can't say about TI :P
Spoiler For EDIT:
400th post!!!!1!!1111!one
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Eiyeron on October 21, 2011, 01:22:33 pm: Agreed! :p
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 21, 2011, 01:35:57 pm: Has the size limit of add-ins been increased/removed? Physium is over a megabyte!
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Eiyeron on October 21, 2011, 01:37:43 pm: Visibly, yes!
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: ztrumpet on October 21, 2011, 03:59:15 pm: Moved to News. This is awesome! :D
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Jim Bauwens on October 21, 2011, 04:03:08 pm: Quote from: turiqwalrus on October 21, 2011, 01:06:35 pm
Quote from: JosJuice on October 21, 2011, 12:40:34 pm
It's wonderful to know that Casio are listening to us and fixing the bugs. It truly feels like they care about everything, and that's great!
which is one thing that we can't say about TI :P
To be honest, they are busy fixing bugs that Adriweb/Levak/Critor and I reported ;)
Anyway, very nice update :)
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Juju on October 21, 2011, 04:03:26 pm: Awesome! :D
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 21, 2011, 04:05:48 pm: Quote from: jimbauwens on October 21, 2011, 04:03:08 pm
Quote from: turiqwalrus on October 21, 2011, 01:06:35 pm
Quote from: JosJuice on October 21, 2011, 12:40:34 pm
It's wonderful to know that Casio are listening to us and fixing the bugs. It truly feels like they care about everything, and that's great!
which is one thing that we can't say about TI :P
To be honest, they are busy fixing bugs that Adriweb/Levak/Critor and I reported ;)
Anyway, very nice update :)
They seem to be interested in fixing the Nspire, but the z80 series still has many ancient bugs left that we know how to fix, such as group corruption.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Jim Bauwens on October 21, 2011, 04:09:19 pm: Ah, wasn't thinking about the other calculators. In that case you might have a point.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: DJ Omnimaga on October 21, 2011, 04:16:57 pm: It was about time! I e-mailed them about the bug in Jan or Feb I think and they said it would be fixed in the next update. However the update never came until now X.x

Does C/ASM stuff still work on it, such as Obliterate? I hope Casio won't try blocking games X.x

Also can somebody post this on Cemetech?
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 21, 2011, 04:20:15 pm: Quote from: DJ_O on October 21, 2011, 04:16:57 pm
Does C/ASM stuff still work on it, such as Obliterate? I hope Casio won't try blocking games X.x
Everything seems to work just like before (I tried Minesweeper and Obliterate).
Quote from: DJ_O on October 21, 2011, 04:16:57 pm
Also can somebody post this on Cemetech?
I posted it there recently.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: DJ Omnimaga on October 21, 2011, 04:27:03 pm: Ok good to hear. And thanks, I didn't see it.

EDIT: Wait what?

Quote
- Exp>Str() bug (System error)

Does Exp refers to Y= equations? If so, then it's kinda funny how both TI and Casio had bugs with such command. On the 83+, Equ>Str had some weird bugs that could cause RAM corruption and mem clears back in OS 1.14 or below. They were also present on the 82, 82 STATS, 83 and 76.Fr.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Munchor on October 21, 2011, 04:56:46 pm: Casio is listening to us, but TI is not really... I think these companies should listen more to developers and even have like an infiltrated guy (but we would know who he is) that asks us what we want and need.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: DJ Omnimaga on October 21, 2011, 04:57:25 pm: Quote from: cfxm on October 21, 2011, 04:53:53 pm
Not exactly. Some bugs are described here (in German): http://www.casiofans.de/viewtopic.php?f=50&t=3681
Ah ok I see.

Also wow Physium add-in is over 1.5 MB large! O.O
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Darl181 on October 21, 2011, 06:32:50 pm: Nuu you need admin privileges to update :|/me stabs school computers
I guess it works like the 9860 when updating?

Looks like it'll help, tho. I've been wondering when the Locate() bug would be fixed :D
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: m1ac4 on October 21, 2011, 10:42:41 pm: I have a laptop that runs Ubuntu (11.10) and have been trying to update the OS using WINE and it hasn't been working. Is there anything I can do to make it work? Otherwise, I can wait until I have access to a Windows machine to do it.
Edit: It looks like the computer is simply not recognizing the connection, it's worked before so I'll just reboot. Never mind, I will just wait until tomorrow.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 22, 2011, 05:38:28 am: Quote from: m1ac4 on October 21, 2011, 10:42:41 pm
I have a laptop that runs Ubuntu (11.10) and have been trying to update the OS using WINE and it hasn't been working. Is there anything I can do to make it work? Otherwise, I can wait until I have access to a Windows machine to do it.
Edit: It looks like the computer is simply not recognizing the connection, it's worked before so I'll just reboot. Never mind, I will just wait until tomorrow.
I don't think that anyone has been able to update the Prizm OS using Wine. Since it most likely uses its own drivers to communicate with the calc, Wine might not support it at all.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: m1ac4 on October 22, 2011, 10:28:52 am: I suspected as much. I am still getting used to using a non-Windows OS.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: 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
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: Darl181 on October 22, 2011, 06:23:56 pm: Seems to me there's a new font, "Minimini Char", in the test menu that Insight can bring up. Looks like it's the font used in Physium.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: DJ Omnimaga on October 22, 2011, 07:44:10 pm: 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
Yeah true. I just hope they continue keeping app creation by third parties possible. Eg: Obliterate still works fine. I'm sure if that calc was TI, Obliterate would have stopped working by now.

Also I'm confirming that the Locate bug was definitively fixed. Now BASIC coders got the following chars freely available for use in their games!
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: 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 (http://www.omnimaga.org/index.php?action=dlattach;topic=5610.0;attach=7463) was written to extract it. Is this DLL file still present? I haven't been able to look at the 1.03 MSI yet.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: alberthrocks on October 23, 2011, 11:43:34 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 (http://www.omnimaga.org/index.php?action=dlattach;topic=5610.0;attach=7463) was written to extract it. Is this DLL file still present? I haven't been able to look at the 1.03 MSI yet.
Nope, doesn't exist at all. It all kinda exists inside the MSI, oddly enough. Maybe I'm wrong, though...

Here is the file list for the MSI:
Code: [Select]
Directory of D:\Documents and Settings\albert\My Documents\Downloads\MSIDump\MSIDump 10/23/2011 10:39 AM <DIR> . 10/23/2011 10:39 AM <DIR> .. 10/23/2011 10:00 AM 420 !ActionText 10/23/2011 10:00 AM 78 !AdminExecuteSequence 10/23/2011 10:00 AM 84 !AdminUISequence 10/23/2011 10:00 AM 120 !AdvtExecuteSequence 10/23/2011 10:00 AM 92 !Binary 10/23/2011 10:00 AM 8 !CheckBox 10/23/2011 10:00 AM 36 !Component 10/23/2011 10:00 AM 9,932 !Control 10/23/2011 10:00 AM 584 !ControlCondition 10/23/2011 10:00 AM 1,680 !ControlEvent 10/23/2011 10:00 AM 4 !CreateFolder 10/23/2011 10:00 AM 156 !CustomAction 10/23/2011 10:00 AM 660 !Dialog 10/23/2011 10:00 AM 60 !Directory 10/23/2011 10:00 AM 2,448 !Error 10/23/2011 10:00 AM 120 !EventMapping 10/23/2011 10:00 AM 16 !Feature 10/23/2011 10:00 AM 12 !FeatureComponents 10/23/2011 10:00 AM 36 !File 10/23/2011 10:00 AM 4 !Icon 10/23/2011 10:00 AM 462 !InstallExecuteSequence 10/23/2011 10:00 AM 174 !InstallUISequence 10/23/2011 10:00 AM 10 !ISComponentExtended 10/23/2011 10:00 AM 54 !ISCustomActionReference 10/23/2011 10:00 AM 12 !ISSetupFile 10/23/2011 10:00 AM 4 !LaunchCondition 10/23/2011 10:00 AM 12 !Media 10/23/2011 10:00 AM 12 !ModuleComponents 10/23/2011 10:00 AM 6 !ModuleSignature 10/23/2011 10:00 AM 324 !Property 10/23/2011 10:00 AM 234 !RadioButton 10/23/2011 10:00 AM 264 !TextStyle 10/23/2011 10:00 AM 200 !UIText 10/23/2011 10:00 AM 1,360 !_Columns 10/23/2011 10:00 AM 143,759 !_StringData 10/23/2011 10:00 AM 11,292 !_StringPool 10/23/2011 10:00 AM 78 !_Tables 10/23/2011 10:00 AM 5,352 !_Validation 10/23/2011 10:00 AM 169,272 Binary.ISSELFREG.DLL 10/23/2011 10:00 AM 1,859,935 Binary.ISSetup.dll 10/23/2011 10:00 AM 58,680 Binary.ISSetupFilesHelper 10/23/2011 10:00 AM 1,033 Binary.NewBinary1 10/23/2011 10:00 AM 4,534 Binary.NewBinary10 10/23/2011 10:00 AM 4,534 Binary.NewBinary11 10/23/2011 10:00 AM 3,262 Binary.NewBinary12 10/23/2011 10:00 AM 766 Binary.NewBinary13 10/23/2011 10:00 AM 766 Binary.NewBinary14 10/23/2011 10:00 AM 766 Binary.NewBinary15 10/23/2011 10:00 AM 766 Binary.NewBinary16 10/23/2011 10:00 AM 766 Binary.NewBinary17 10/23/2011 10:00 AM 766 Binary.NewBinary18 10/23/2011 10:00 AM 318 Binary.NewBinary2 10/23/2011 10:00 AM 15,368 Binary.NewBinary21 10/23/2011 10:00 AM 3,340 Binary.NewBinary22 10/23/2011 10:00 AM 318 Binary.NewBinary3 10/23/2011 10:00 AM 3,262 Binary.NewBinary4 10/23/2011 10:00 AM 4,534 Binary.NewBinary6 10/23/2011 10:00 AM 766 Binary.NewBinary7 10/23/2011 10:00 AM 766 Binary.NewBinary8 10/23/2011 10:00 AM 10,134 Binary.NewBinary9 10/23/2011 10:00 AM 128,320 Binary.SetAllUsers.dll 10/23/2011 10:00 AM 418,098 Data1.cab 10/23/2011 10:00 AM 110,592 Icon.ARPPRODUCTICON.exe 10/23/2011 10:00 AM 7,871,488 ISSetupFile.SetupFile1 10/23/2011 10:00 AM 65,536 ISSetupFile.SetupFile2 10/23/2011 10:00 AM 612 [5]SummaryInformation(I removed some entries because there were other files and folders created, hence no total stats are shown here.)

The Data1.cab file also has nothing of interest - they are just Microsoft VC(++) redistributables:
Code: [Select]
Directory of D:\Documents and Settings\albert\My Documents\Downloads\MSIDump\MSIDump\CABFILES 10/23/2011 10:39 AM <DIR> . 10/23/2011 10:39 AM <DIR> .. 03/18/2010 09:15 AM 421,200 F_CENTRAL_msvcp100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C 03/18/2010 09:15 AM 770,384 F_CENTRAL_msvcr100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C 4 File(s) 1,191,900 bytes(note the msvcp100 and msvcr100)

Using the handy-dandy GNU file program, I got this data (some omitted again, due to extra files placed inside):
Code: [Select]
!_Columns; data !_StringData; Non-ISO extended-ASCII English text, with very long lines, with CRLF line terminators !_StringPool; data !_Tables; data !_Validation; data !ActionText; data !AdminExecuteSequence; data !AdminUISequence; data !AdvtExecuteSequence; data !Binary; data !CheckBox; data !Component; data !Control; data !ControlCondition; data !ControlEvent; data !CreateFolder; data !CustomAction; data !Dialog; data !Directory; data !Error; data !EventMapping; data !Feature; data !FeatureComponents; data !File; data !Icon; data !InstallExecuteSequence; data !InstallUISequence; data !ISComponentExtended; data !ISCustomActionReference; data !ISSetupFile; data !LaunchCondition; ASCII text, with no line terminators !Media; MIPSEB Ucode !ModuleComponents; data !ModuleSignature; data !Property; data !RadioButton; data !TextStyle; data !UIText; DOS executable (COM) [5]SummaryInformation; Unicode text, UTF-32, big-endian Binary.ISSELFREG.DLL; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit Binary.ISSetup.dll; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit Binary.ISSetupFilesHelper; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit Binary.NewBinary1; JPEG image data, JFIF standard 1.02 Binary.NewBinary10; MS Windows icon resource - 2 icons, 48x48, 256-colors Binary.NewBinary11; MS Windows icon resource - 2 icons, 48x48, 256-colors Binary.NewBinary12; MS Windows icon resource - 1 icon Binary.NewBinary13; MS Windows icon resource - 1 icon Binary.NewBinary14; MS Windows icon resource - 1 icon Binary.NewBinary15; MS Windows icon resource - 1 icon Binary.NewBinary16; MS Windows icon resource - 1 icon Binary.NewBinary17; MS Windows icon resource - 1 icon Binary.NewBinary18; MS Windows icon resource - 1 icon Binary.NewBinary2; MS Windows icon resource - 1 icon Binary.NewBinary21; JPEG image data, JFIF standard 1.01 Binary.NewBinary22; JPEG image data, JFIF standard 1.01 Binary.NewBinary3; MS Windows icon resource - 1 icon Binary.NewBinary4; MS Windows icon resource - 1 icon Binary.NewBinary6; MS Windows icon resource - 2 icons, 48x48, 256-colors Binary.NewBinary7; MS Windows icon resource - 1 icon Binary.NewBinary8; MS Windows icon resource - 1 icon Binary.NewBinary9; MS Windows icon resource - 6 icons, 16x16, 16-colors Binary.SetAllUsers.dll; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit Data1.cab; Microsoft Cabinet archive data, 418098 bytes, 2 files Icon.ARPPRODUCTICON.exe; PE32 executable for MS Windows (GUI) Intel 80386 32-bit ISSetupFile.SetupFile1; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit ISSetupFile.SetupFile2; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit
And the Data1.cab:
Code: [Select]
F_CENTRAL_msvcp100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bit F_CENTRAL_msvcr100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C; PE32 executable for MS Windows (DLL) (GUI) Intel 80386 32-bitObviously, I was right about those files being redistributables.
This is something interesting to explore... though I'm not sure if we should be pissing Casio off or not... maybe they'll give us specs? :P

(Sidenote: Seeing that other topic (http://ourl.ca/8207) is the center for Casio hacking discussion, should I move the discussion to there?)
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 23, 2011, 11:50:02 am: Maybe the DLL was outside of the MSI? The only thing I'm sure about is that I found it in the temp folder.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: alberthrocks on October 23, 2011, 12:10:45 pm: Quote from: JosJuice on October 23, 2011, 11:50:02 am
Maybe the DLL was outside of the MSI? The only thing I'm sure about is that I found it in the temp folder.
I'll try "installing" it later - this computer doesn't let me have admin privileges, which is required for installation.
/me pokes Casio to make a TI-Connect, but 1000x better :P

EDIT: Note that I don't have a CASIO Prizm... but I can see if I can get those files out since you said that they are copied to the TEMP folder.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice on October 23, 2011, 01:56:04 pm: Quote from: alberthrocks on October 23, 2011, 12:10:45 pm
/me 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.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: 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
/me 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...
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: JosJuice 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
/me 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.
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: TIfanx1999 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. =)
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: MPoupe 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 ?
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: z80man 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?
Title: Re: OS 1.03 and PHYSIUM add-in
Post by: bsl 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 (http://www.omnimaga.org/index.php?action=dlattach;topic=5610.0;attach=7463) 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