English Amiga Board - View Single Post

gibs · 29 December 2011, 20:27

@Nostromo
Ah yes, the problem was spaces in volume names. I'm going to send an update in a few minutes, so you can test. I have also improved many things...

For the moment put tinylauncher.exe at the first line of your startup-sequence.
I know that a few demos doesn't run like that (starstruck from TBL) but it also doesn't work from the early startup, so it's not the Tiny's fault.

Later I'll look to do for a better startup-sequence but actually I put TinyLauncher.exe at the 1st line. Olesio is the Startup-sequence's guru

look at his examples in this thread.
I'm sure he can help you if you want to do a better tuning but in my case I put TL in the 1ST line or before Binddrivers, so RAM:ENV and RAM:T are assigned...

29 December 2011, 20:27	#352
gibs Banned Join Date: Jan 2010 Location: france Posts: 932	@Nostromo Ah yes, the problem was spaces in volume names. I'm going to send an update in a few minutes, so you can test. I have also improved many things... For the moment put tinylauncher.exe at the first line of your startup-sequence. I know that a few demos doesn't run like that (starstruck from TBL) but it also doesn't work from the early startup, so it's not the Tiny's fault. Later I'll look to do for a better startup-sequence but actually I put TinyLauncher.exe at the 1st line. Olesio is the Startup-sequence's guru look at his examples in this thread. I'm sure he can help you if you want to do a better tuning but in my case I put TL in the 1ST line or before Binddrivers, so RAM:ENV and RAM:T are assigned...