just started using a copy of my own rom/ Kickstart image and now during boot I get a requester asking for ENV. I cant find anything that is asking for it in the startup before the assign has been made in the second startup-sequence. Really annoying problem. Anyone else experienced this ????

[ Edited by LawlessPPC on 2006/4/25 20:05 ]

Kickstart image, what system is this?

Anyway, why are you messing around with the ENV assigns? Just leave
them in the beginning of startup-sequence where they always are by
default.

"Kickstart image, what system is this?"

what? don't you know? its a modified 1.7Ghz AmigaOne..what else?

in answer to the question what system is this? Look at the forum its in. Its a1200 all singing. I havnt touched a single assign regarding ENV.

Sorry if this sounds blunt but why comment in this way especially as you are so off par its untrue.

If you are not aware of this problem or have no idea what I'm on about then please dont hinder the process of me aleast trying to find a solution.

Sorry, I missed the forum name (saw the post on main page).

But really, I do doubt that ENV: should be set up in user-startup. It
is needed by system components launched in startup-sequence and I
can't see why it should (or how it could) have been removed from
startup-sequence in the powerup release.

You could use a tool such as SnoopDos to find out exactly what uses
ENV:.

But I meant to be helpful and I still very much believe that ENV:
should be set up very early in startup-sequence.

apologies Merko. I have just re read my original post and edited it accordingly. I put user startup where it should have been startup-sequence. Of which on the powerup version it executes 2. The first one just kinda resets the amiga and makes certain modules resident including my rom / kickstart image. The second startup-sequence does all the usual few assigns in memory launch monitor drivers etc. Perhaps people may be able to help now they kow what my problem or circumstances really are

@LawlessPPC

Sorry can't help, but I have exactly the same problem trying to get MOS PUP to work on my A4000 with CS PPC.? Just thiught I'd let you know.

@TrevorDick

I have no problems getting morrph to boot at all in fact it is now the
only OS I run. Ive just done a fresh install of it because I got a
fresh 73GB U320 scsi hardrive. No probs this time with the rom image
but I have no assigns made yet inn the startup so hopefully this time
when I make the new assigns I may find the problem. I've a sneaky
suspicion it may have been easynet/amitcp that may have caused the env
problem. It would still continue to boot when I clicked cancel when it
asked for volume env.

i've already heard about this ENV problem. IIRC its due a truncated S-S (i.e if you have edited the S-S with ED) and/or a filesystem that doesn't support long filenames.

@LawlessPPC

Glad to hear you have MOS PUP up & running. I'm still having problems however and can't seem to get past the first stage. I can't even boot of the PUP CD-ROM. I would be grateful for any advice you could give. I would like to get it running but after spending the best part of 3 days working on it I'm about to bin the idea and stick with OS3.9.



[ Edited by TrevorDick on 2006/5/25 19:37 ]

@TrevorDick
Please tell the full config of the system you are trying to run it on
including if its an ide drive you are trying to boot of or scsi

@LawlessPPC

The A4000 I am using has both ide and scsi (fastlane interface) HDD's. I first tried staright from the CD-ROM and the scsi drive following the simple startup instructions. No joy.

I then repartitioned the scsi with SFS and copied the cd-rom to the low priority boot partition. I attempted to (manually) boot off the selected scsi partition. No joy.

I tried endless edits of the startup sequence - No joy

I tried boot from the ide/ CDRom combination - No joy.

I am now going to copy the contents of the PUP cd-rom to a bootable partition om the ide HDD and attempt to boot again.

The ide drive has the standard AOS ffs.

My completer setup is:-

Cyberstorm PPC/230e/060 with CS 64/3D, 18MB ram on A4000, 64MB ram on CS and 64MB on fastlane card.

The system works fine under OS3.9.

Update: Manually booting of the internal ide drive (ffs system) and guess what? MorphOS boots up without any changes to the startup-sequence!!

I need to create at least 16bit screen mode for ambient as only an 8-bit mode seems to be included, but at leasy I seem to be making progress.



[ Edited by TrevorDick on 2006/5/25 20:49 ]

[ Edited by TrevorDick on 2006/5/25 20:51 ]

OK I'm almost there I think?

I can boot up MorphOS and the intro splash screen is displayed (butterfly & MorphOS) then I get a requester telling me to set up a 16/24bit screen mode for Ambient. However only 8bitCV64/3D sceen modes are displayed in screen mode window. I copied my monitor prefs from the Amiga OS3.9 side which has 1024x768 16/24 bit modes but these don't seem to show up in the screemode utility. Therefore I can't run Ambient. I can run a shell window and have full access and control of all the facilities under morphos but not the ambient screen. I presume this is a simple fix? Can anyone advise how I might obtain access of the 16/24 bit modes on bootup to enable me to run ambient. Thanks.

[ Edited by TrevorDick on 2006/5/25 22:41 ]

EUREKA!!!!!!!!!!!!!!!!!!!!

Copied cybervison3dmonitor prefs from my OS3.9 system to the sys:prefs/env-archive/cybergraphx directory and all now works OK. Unbelievable

Thanks to those who made useful suggestions.

You probably must visit ModeEdit (MOSSYS:Prefs/Preferences).

(Edit: ok, too late.)

[ Edited by itix on 2006/5/26 1:37 ]

@itix

Quote:

Thanks but that was my problem. I couldn't run ModeEdit without Ambient running and I couldn't run Ambient without the correct screen mode? (A bit like "theres a hole in my bucket").

Is there a wat of running ModeEdit from a shell window?

To get ModeEdit:
CD MOSSYS:Prefs/
Preferences mprefs/ModeEdit.mprefs

To get all prefs:
MOSSYS:Prefs/Preferences