You shouldn't need anything of the above. Just cancel the ENV requesters. Or enter assign env: ram: to avoid the requesters.

Well, please remove the >nil: from the version commands and tell us the error message that appears.

Bye,
Thomas

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

duplicate post deleted

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

Quote:

You shouldn't need anything of the above.

Well that depends. It is possible to loadwb without ENV: set up properly. But the prefs won't work properly that way.

Those commands I posted won't work though, and I won't bother reposting as the respective (2.1 & 3.1) startup sequences should handle this.

Well, I found the error. The older version of the Version command does not accept the VERSION keyword but works without.

So remove the duplicate word "version" from all the Version commands.

Later versions of the Version command try to open a file named "40" if you enter "version 40" so they need the VERSION keyword in front of the number.

Bye,
Thomas

P.S. I hope I could confuse you with all these versions

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

@salass00

The thing is, each individual startup-sequence for each workbench should set up ENV: properly for you, so that shouldn't have anything to do with the multiboot scripts since they all still use the standard startup-sequence.

_________________
Playstation Network ID: xeron6

Using onyl one "version" command, it works flawlessly!!

WOOT!!!

JIPPIIEEEE!!!

Now I am going to delete stuff from root, delete the .info of the HDD and keep the Drawers "OS13", "OS21" and "OS3" out ...

This is going to be fun!

Thanks a LOT to all who helped me!

Danke Thomas!

McTrinsic

_________________
-------------------------------------
Banquo Dragon of the UDIC

Quote:

salass00 wrote: Quote: With OS2.1 and OS3.1I can use "loadwb" to get the HDD on the Desktop but get an "ENV not found" error; with OS13 nothing happens at all.... Before "loadwb" you'll need to do this: makedir >NIL: ram:env assign env: ram:env assign envarch: SYS:Prefs/env-archive copy >NIL: envarch:#? all env: I haven't tried it but I think that should work...

This has been solved by the fact that boot script now works and lets me boot into OS13, OS21 or OS3 depending on my KS without any problem, so i dont have to use "loadwb" manually anyway.

Only thing I noticed is that the message "Intuition will be resetted" or "Program ??? tries to reset Intuition" or something similar flashes two times, but I dont get a chance to press "cancel " or "ok" or whatever option this dialogue gives... This only briefly appears, then is gone and everything seems to be ok.


McTrinsic

_________________
-------------------------------------
Banquo Dragon of the UDIC

duplicate post deleted

Sorry

_________________
-------------------------------------
Banquo Dragon of the UDIC

Quote:

"Program ??? tries to reset Intuition"

There are some programs in your startup script which write output to the CLI window. The requester appears if the CLI window is open when Intuition tries to change the screen mode and disappears when the window is closed.

Just add >nil: to the commands with output so the screen stays dark until Workbench is loaded.

Bye,
Thomas

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

Well it's the very original, untouched startup-sequence from the OS3.1 install.

Since I have no idea what command does what, I will just leave it alone.

I was just sort of surprised to find such messages after a clean install.


Have fun,
McTrinsic

_________________
-------------------------------------
Banquo Dragon of the UDIC

Sorry, I stand corrected.

Under KS1.3 it DOES NOT work.

I get the following error:

"Error in open
Version failed returncode 10"

Seems like the very first version command causes the error.

I did use the assign:C ... line from Thomas at the very top of the s-sequence.

Any ideas?




McTrinsic

_________________
-------------------------------------
Banquo Dragon of the UDIC

It means it has tried to open it as a file and failed, I think. Try "version >NIL: exec.library ??". Swap the ?? for the version numbers.

[edit]
Argument syntax of version from the 1.3 AmigaDOS manual:
Quote:

VERSION <library name/device name> [<version #>] [<revision #>] [<unit #>]

Quote:

Argument syntax of version from the 1.3 AmigaDOS manual:

Yes, exactly that is the problem. The syntax has changed somewhere between 1.3 and 3.1 (probably with 2.0).

So make sure the C: assign points to os13/c and use C:Version instead of just Version.

Bye,
Thomas

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

Ok, its almost perfect now.

Unfortunately, only "almost" :(

When booting into OS13 using KS1.3, the very last command won't execute. I traced it back to this last one.

The shell window simply looks as if it would do nothing.

When I enter "C:execute s:startup-sequence" for the first time, I get an error message, saying execute cant execute the startup sequence, doing it a second time will boot into OS13 nicely.

Doesnt matter if it is C:execute or execute alone.

Grumble... and it ALMOST worked!


McTrinsic

_________________
-------------------------------------
Banquo Dragon of the UDIC

Are you sure that is the exact message? I've tried many times unsuccessfully to get that message with wb1.3 under UAE (using both files that do not exist and binary files).

I did find one interesting thing in the 1.3 AmigaDOS manual on execute:
Quote:

EXECUTE now uses the logical name T: if it is ASSIGNed; otherwise it uses :T directory.

I've tried removing both in the hope of producing an error message but so far it hasn't worked (that means it still worked).

You could still try adding "assign T: RAM:" just before the execute command though.

I apoligize dearly, sorry, I found the fault, was my wrong.

I used "TurboText" to edit and write the startup-sequence.

While KS2.04 and KS3.1 did not bother, KS1.3 had a problem with the fact that the last line ended with some special character. Maybe it was a line feed or end of file or something like this. I added a few empty lines and everything works now.

So what i want to say is:

THANKS A VERY LOT PEOPLE!!!!

WOOOOOOT!




McTrinsic

_________________
-------------------------------------
Banquo Dragon of the UDIC

good to see yet another problem solved

_________________
Founder of NWAG - North West Amiga Group

Night Operations

A1200 020/28MHz + 64Mb / 4Gb CF / OS 3.1.4.1 / 1438S
A500+ / 2Mb
A600