Tiny Launcher 1.0 Released

[gibs]

@emuola
Where it crash ?

[KTC]

Originally Posted by emuola

I have Newicons enabled in the ClassicWBFull, and it always crashes. Weird. Let's see the next version

I could always see the NewIcons, but I guess that is because Scalos can handle it without the running the NewIcons executable.

Could you please try booting into workbench, navigate to C folder and run the executable NewIcons.
After that, try running Tiny Launcher and launch something that would normally crash.
Does it work then?

[KTC]

Originally Posted by gibs

Hold on. I'm fixing the RetroNerd issue first.

Yes of course. I hope you know that I don't mean to stress you, only help with as much constructive information as possible for you to track down the bugs fast.

My biggest problem right now is getting Tiny Launcher to run in my startup-sequence along with the NewIcons executable. Tiny Launcher makes my Workbench/Scalos mess up if I put it too late in the startup-sequence, where NewIcons fails if I put it in too soon. So as I have to run NewIcons before Tiny Launcher, I have a bit of a paradox.

[Retro-Nerd]

I can confirm a Guru/Software failure, after i've disabled the New Icons in ClassicWB Lite.

[emuola]

Could you please try booting into workbench, navigate to C folder and run the executable NewIcons.
After that, try running Tiny Launcher and launch something that would normally crash.
Does it work then?

IT WORKS!!! Yippikayee

I can confirm that the Newicons is the culprit here. Now, how do we get that to the early startup..?

[KTC]

Finally!

I found a way to make it work from my startup-sequence.
This code will launch Tiny Launcher before your system loads Workbench, giving you quick access to your demos and games and stops your Amiga using lots of resources. I also added an assign because it fixed the problem with Workbench (Scalos) messing up after exiting Tiny Launcher.

My setup is running Tiny Launcher from the C folder of my system drive on a Classic Workbench v27 Full installation. I cannot guarantee that this will work as well on other setups, so don't blame me if it doesn't work on yours. All the following is to be used on your own risk

Open up the S:Startup-sequence file in an editor and put the following codes in order just before the C:LoadWB line, or alternatively put the lines somewhere in your User-startup file:

In the Lite version of Classic Workbench (v27) it already runs NewIcons in the User-Startup, and the problem with Scalos if also not present as it runs a real Workbench, so here you can skip the following changes and just put in your TinyLauncher executable line.


This line runs NewIcons so Tiny Launcher can utilise it. If you get a message saying "Already running!", you already have NewIcons in your startup files, and then you can skip it:

Run <>NIL: C:NewIcons

This line is needed, as NewIcons does not seems to initialize before the cli or wb screen is shown:

Echo "Running Tiny Launcher"

The following line runs Tiny Launcher.
If you are using another version of Tinylauncher or another path, please change the name and path of the exe file to match your setup:

C:tinylauncher22b40.exe

I added this assign because it fixed the problem with Scalos messing up after running Tiny Launcher at startup. You can try running without it and just put the line in if your Scalos doesn't run properly after exiting Tiny Launcher:

Assign >NIL: ENV: RAM:ENV

If you get a System Request saying that "Intuition is attempting to reset the Workbench screen.", you have probably put the lines too soon in your startup-sequence. Move the lines down before C:LoadWB or into the User-Startup file, and you should be good.

[emuola]

Thank you for the solution

I made another possible "solution" based on KTC's one and by doing the following:

1. Start SYS:System/BMenu/Buttonmenu
2. Open Menus/Runlist
3. Add a New Item for example called TinyLaucher and the DOS command:

SYS:path_to_your_TL/TinyLaucher.exe

4. Tick "Run command in background"
5. Save

Edit SYS:S/Runlist-Startup and add the following line:

Run <>NIL: C:NewIcons

Reboot, hold RMB and select Runlist -> TinyLauncher

~1800 KB Chip and ~64400 Fast free

This assumes that you're running the (latest) ClassicWB

[gibs]

You can also use AmigaBootSelector
[ Show youtube player ]

[emuola]

Originally Posted by gibs

You can also use AmigaBootSelector
[ Show youtube player ]

Yes, I'll try that also Thank you Gibs for these 2 magnificient apps (TL & ABS) for the Amiga

[gibs]

http://dl.dropbox.com/u/1566495/Tiny...ncher22b42.exe

Ok, this version fix the crash at start if S:TinyLauncher isn't created and also no more crash while scanning. I promise if Retronerd crash while scanning I sent him a beer.

To test it seriously, I had to put DH0: to scan (huge tree)... no problem.

So there are still bugs. like if you change a path and you scan an empty area, it keep the old scan...an others. but I'm going to fix all. It took time to rewrite this routine, but I'm probably going to write it again to see If I can support long slaves filenames like AlienBreedTowerAssaultAGA.Slave

I don't know how it is possible to test the presence of a long file like this, if someone have a clue, tell me... Or I will probably have to cheat like I did in the 2.1 version and earlier...

[Retro-Nerd]

Now it starts and scan the A-Z folder, but it still crashes after the "Z" folder and created no database. 1st Level scan took app 3 minutes, the 2nd Level 10-15 minutes. It scans now for everything, data, readme, slaves etc?

Edit: Just tried a single folder scan again and got a I/O error from the WB.

[gibs]

damn, it's impossible !!! I owe you a beer !
can you try to move out your tiny launcher directories from the directory you scan (I have seen that in your previous logs)?
delete the old database.

[Retro-Nerd]

I've deleted already the S:TinyLauncher files. Doesn't work. I'v also moved the TinyLauncher.exe to DH0:

[gibs]

move out your tinylauncher directories from the directory you scan.

[Retro-Nerd]

I had no TinyLauncher directory in the game partition, only a few TL betas. Moved them already. After the scan i can enter the gamelist, it shows 0 games and crashes immediately.

Edit: Just forgot it. I get a "nothing found" now during the 1st level scan. Also single folder scans doesn't work for me anymore, i always get a I/O error at the end of the scan.

[SuperNashwan]

Just tested 2.2b40 on winUAE, classicWB lite, as described before. Loading from workbench, not early startup.

Demos work fine. Single level scan completes and demos launch with tooltypes.

Games don't finish second level scan. Quits to WB at around 2700 files. A .db files is created for the games but only goes up to midway thorugh the W folder (Winter Games!).

[gibs]

B42 is different. Can you try ?

@RetroNerd can you do a directory with 10 games, and try ?
If it fail reduce the number, if it doesn't increase...
Just to understand where it comes from.

[emuola]

I can confirm that b42 scans happily all the way (~2060 slaves), but crashes after the scan (when entering the main screen) and database shows 0 games. This is both with latest Winuae and real A1200 both with latest ClassicWBFull.

[gibs]

ok. I confirm.

http://dl.dropbox.com/u/1566495/Tiny...ncher22b43.exe

Started like the first time.
Create 1 DB of 1 level
Create 1 DB of 2 levels
Both are displaying & launching.

(Long filenames not detected).

[Retro-Nerd]

Finally the A-Z folder scan works for me, with the 2nd level scan. Thanks for fixing this patiently.