Updated port of SQLite

I updated via packman and re-started; it went boom!

A bit more WimpSlot looks to be needed, increase WimpSlot -min to 1280K. That worked on a Titanium.

Sorry! I thought about that yesterday while I was waiting for the tests to run, but ultimately forgot to change it. The download links above have now been updated, and a fixed package is on its way. If you’ve hand-edited !Run then PackMan might get confused if you don’t change it back.

Thank you for the updates on the crash; I can increase the Next memory slot in the Tasks window, as well. It works; thanks again for the tips.

Packman updated the application, and it has the same problem; I also tried a reinstallation.

Hmm. Does it fail as soon as you run the SQLite app, or is it when you do something with a database? Can you confirm that your !Run file is now specifying a minimum of 1280k (instead of 1024)? What did you manually set the Next slot to earlier?

Yes, it fails immediately. If I set Next manually to 1280K, it works and keeps on working. However, it crashes if I set it to the same value in the Run file. Before that, I was dragging Next to a random spot over 2000K.

How bizarre! Can you please try setting 1536 in the !Run file and see whether that helps? It’s happy with 1280 on my machine so I wonder why it doesn’t like it on yours.

Error message:

06:53:44.50 Exec
06:53:44.50 <SQLite$Dir>.sqlite3 
06:53:44.53 ** Error **
  Error  : &80000002
  Message: Internal error: abort on data transfer at &00136F84
06:53:44.53 ** WimpError ** from TaskWindow
  Error  : &80000002
  Message: Internal error: abort on data transfer at &00136F84
06:53:44.53 Exec
06:53:49.74 Exec
Address &00136F8C is not in any module.
Register dump (at &2005A210) is:
pc  = &00136F8C  Flags=&20000110=nzCv if  Mode=User 32 bit
r0  = &1B496F6B : koI. :  457797483
r1  = &98BBEEA2 : ¢î»— : 2562453154
r2  = &A0E3BD47 : G½ã  : 2699279687
r3  = &A5170E11 : ...¥ : 2769751569
r4  = &E24CB004 : .°Lâ : 3796676612
r5  = &E15D000A : ..]á : 3780968458
r6  = &000080D4 : Ô€.. :      32980
r7  = &00136FF4 : ôo.. :    1273844
r8  = &000082C0 : Àŵ.. :      33472
r9  = &00136FB4 : ´o.. :    1273780
r10 = &001370DD : Ýp.. :    1274077
r11 = &00135284 : ✘R.. :    1266308
r12 = &00133684 : ✘6.. :    1259140
r13 = &000000E9 : é... :        233
r14 = &00008004 : .€.. :      32772
Code around address is:
00136F54 : Invalid address

abort on data transfer at &00136F84

That is the error that occurs if WimpSlot -min is at the original lower value of 1024K. The later build currently on PackMan, SQLite_3/40/0-2_arm/zip, with WimpSlot -min at 1280K is just fine here. Tested on Titanium, RPCEmu and RP400, and even OS4.02 VRPC.

I have the similar issues.

Upgrade SQLite and it aborts when trying to start.

Delete it and reinstall and the same.

Alter the !Run file -min wimpslot from 1024K to 1280K and it works.

Starting it says 3.40.0 2022-11-16 12:10:08

So bit of checking and Updating the lists gives me the latest version which works without altering the !Run file :-)

Error message:

With which settings in !Run?

So bit of checking and Updating the lists gives me the latest version which works without altering the !Run file :-)

The current package is “3.40.0-2”; anyone having issues should ensure that their PackMan is “seeing” that version.

Tested on Titanium, RPCEmu and RP400, and even OS4.02 VRPC.

Thanks for testing :)

@Chris, I used the one you referenced above.

I have spotted an issue. I have installed the latest Packman version, which claims to be 3.40.0-2. On changing the Next memory slot to run it, it reports 3.40.0 2022-11-16 12:10:08.

I used the one you referenced above.

There have been a couple of different references above, so can you please copy/paste your !Run in here just to double-check everything?

I have spotted an issue. I have installed the latest Packman version, which claims to be 3.40.0-2. On changing the Next memory slot to run it, it reports 3.40.0 2022-11-16 12:10:08.

That’s correct. The new package doesn’t have any changes to the SQLite binary, just the !Run file.

Set SQLite$Dir <Obey$Dir>
Set SQLite$Path <SQLite$Dir>
IconSprites <SQLite$Dir>.!Sprites
Set Alias$@RunType_A70 Run <SQLite$Dir>.!Run %%*0
Set File$Type_A70 SQLiteDB

RMEnsure UtilityModule 3.10 Error SQLite requires RISC OS 3.10 or later
RMEnsure UtilityModule 3.70 RMEnsure CallASWI 0.03 RMLoad System:Modules.CallASWI
RMEnsure UtilityModule 3.70 RMEnsure CallASWI 0.03 Error SQLite requires CallASWI 0.03 or later
RMEnsure FPEmulator 4.19 RMLoad System:Modules.FPEmulator
RMEnsure FPEmulator 4.19 Error SQLite requires FPEmulator 4.19 or later
RMEnsure SharedCLibrary 5.17 RMLoad System:Modules.CLib
RMEnsure SharedCLibrary 5.45 Error SQLite requires SharedCLibrary 5.45 or later

WimpSlot -min 1280K -max 2048K
TaskWindow "<SQLite$Dir>.sqlite3 %*0" -quit

The !Run file as per a new installation; no changes. Tasks, Application tasks, Next 640K

@ Andrew

Tasks, Application tasks, Next 640K

As a general rule, on modern machines, you can configure WimpSlot -next to something like 4096k, that will help when copying files (improve performances) and also when using ShareFS (improve’s ShareFS stability).

It also helps when transfering files using !OmniCLient (as a side note).

This because the filer uses the next slot size for its copying operations.

The 640k is something that really was useful only on really really old machines like the Archimedes. Already on the RiscPC it was better to have something like 1024k or 2048k for the next slot.

Just my 0.5c

Set SQLite$Dir <Obey$Dir>
Set SQLite$Path <SQLite$Dir>

Not related to Wimp slots, but can I just throw into the mix that there’s a vital dot missing from the end of the value being set as SQLite$Path there (and same in the !Boot file).

If I set Next manually to 1280K, it works and keeps on working. However, it crashes if I set it to the same value in the Run file.

This is the bit I don’t understand. It’s as if the WimpSlot command in !Run is being ignored or something. This is a bit beyond me; can any RISC OS experts shed some light on this?

Not related to Wimp slots, but can I just throw into the mix that there’s a vital dot missing from the end of the value being set as SQLite$Path there (and same in the !Boot file).

So there is! Thanks for noticing. I’ve updated my master copy so that’ll be fixed in the next release.

It’s as if the WimpSlot command in !Run is being ignored or something.

Correct. It is.

You’re setting the WimpSlot of the current task, then calling *TaskWindow which will start up a different task (using the Next slot size).

Pass the desired slot size to the TaskWindow command.

Interesting! Thanks for the advice. I wonder why it works for some people (including me) but not others.

Andrew: Can you please try changing the final line to the following, and see whether it fixes it?

TaskWindow "<SQLite$Dir>.sqlite3 %*0" -wimpslot 1280K -quit

I certainly can, Chris. Interlude music. It fixes the error message I posted, and it opens and displays the expected prompt. :)

SQLite version 3.40.0 2022-11-16 12:10:08

On closing the task window that’s opened, I encounter a warning dialogue box with the word Escape.

Paolo: Thank you. $1.00 ;)

It fixes the error message I posted, and it opens and displays the expected prompt. :)

Excellent! I’m glad we got to the bottom of that, and the next release will have !Run fixed.

On closing the task window that’s opened, I encounter a warning dialogue box with the word Escape.

Except your system strikes again! :)

Has anyone else seen that, or know what could cause it?

It is very good to see SQLite making its way to Risc OS. In Linux, Windows, BSD and Mac there is a lovely browser to go with it. Is anybody seeing if they can port that over?

Would you consider providing a link to, or at least giving the name of, this lovely browser?

A quick query produced one, which may or may not be the right one: https://github.com/sqlitebrowser/sqlitebrowser

Indeed, there are several, and I didn’t want to play guessing games.