Welcome, Guest. Please login or register.

Author Topic: Startup-Sequence issues  (Read 3613 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline punkyclownTopic starter

  • Sr. Member
  • ****
  • Join Date: Feb 2002
  • Posts: 262
    • Show only replies by punkyclown
Startup-Sequence issues
« on: July 19, 2009, 01:30:17 AM »
Hi, I seem to have some Startup-Sequence issues, could some one please post their Startup-sequence when running a stock A1200 and OS 3.9, that would be a big help to me.
Also something is wrong with my Path and I can not install anything, every install program I run ends in error with the script not being able to read the C: folder.  When I try to open Shell_VNC first I get a system request to please insert volume IMIMIM. I click cancel and the shell responds with
IMIMIM: device (or volume) not mounted
Path failed return code 10
then I get a prompt and can proceed.  I have never heard of the IMIMIM and I have looked over and over again through the Startup-Sequence for some idea of what it is.
Thank you
 

Offline ZeBeeDee

  • Hero Member
  • *****
  • Join Date: Jan 2007
  • Posts: 1081
    • Show only replies by ZeBeeDee
Re: Startup-Sequence issues
« Reply #1 on: July 19, 2009, 01:38:54 AM »
Both taken from OS3.9

; $VER: Startup-Sequence_HardDrive 45.2 (19.1.2001)
; Startup-Sequence for AmigaOS 3.9

If EXISTS C:SquirrelSCSI
    C:SquirrelSCSI
EndIf

Set SCSIUpdate 1
If EXISTS C:IDEFix
    C:IDEFix
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Expansion/XSurfIDE
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Prefs/Env-Archive/NOSCSIUPDATE
    Set SCSIUpdate 0
EndIf
If $SCSIUpdate EQ 1
    SetPatch QUIET
Else
    SetPatch SKIPROMUPDATES "scsi.device" QUIET
EndIf
Unset SCSIUpdate

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

C:LoadMonDrvs

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

SYS:System/REXXMast >NIL:

IF EXISTS S:User-Startup
  Execute S:User-Startup
EndIF

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:


--------------------

; $VER: Startup-Sequence 45.4 (4.4.2001)
; Startup-Sequence for AmigaOS 3.9

; The following lines disable updating "scsi.device" for driver
; software where this could lead to failures. They also start
; IDEFix if installed.
;
; You can manually disable updating "scsi.device" by setting
; the environment variable "NOSCSIUPDATE" to something.

If EXISTS C:SquirrelSCSI
    C:SquirrelSCSI
EndIf

Set SCSIUpdate 1
If EXISTS C:IDEFix
    C:IDEFix
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Expansion/XSurfIDE
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Prefs/Env-Archive/NOSCSIUPDATE
    Set SCSIUpdate 0
EndIf
If $SCSIUpdate EQ 1
    SetPatch QUIET
Else
    SetPatch SKIPROMUPDATES "scsi.device" QUIET
EndIf
Unset SCSIUpdate

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
Resident >NIL: C:SetEnv PURE REPLACE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

C:LoadMonDrvs

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

SYS:System/REXXMast >NIL:

IF EXISTS S:User-Startup
  Execute S:User-Startup
EndIF

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:
To err is human ... to BOING divine!

[SIGPIC][/SIGPIC]
 

Offline Jose

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show only replies by Jose
Re: Startup-Sequence issues
« Reply #2 on: July 19, 2009, 02:15:22 AM »
Some stuff will be heavily dependant on what you have installed software/hardware wise, so it's not a good idea to use someone else's.
Are you using a disk with installed software from another machine or from another installation of the same machine  (different places for necessary commands etc.) ? If so you'd have to try to configure the software by hand, not easy, could be faster to just reinstall it (provided you have the installers).
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline punkyclownTopic starter

  • Sr. Member
  • ****
  • Join Date: Feb 2002
  • Posts: 262
    • Show only replies by punkyclown
Re: Startup-Sequence issues
« Reply #3 on: July 19, 2009, 02:45:10 AM »
Honestly this first Startup Sequence looks exactly like mine, so that a little funny that mine wants to tell me that I have incorrect number of argument and Unknown file.  What about the IMIMIM volume anybody heard of that.  Thanks for the help.
 

Offline Matt_H

Re: Startup-Sequence issues
« Reply #4 on: July 19, 2009, 04:56:20 AM »
How does your user-startup look? Maybe that's where your trouble is.
 

Offline doctorq

  • Hero Member
  • *****
  • Join Date: Aug 2003
  • Posts: 2082
    • Show only replies by doctorq
Re: Startup-Sequence issues
« Reply #5 on: July 19, 2009, 08:57:51 AM »
@punkycloown

You are aware that OS3.9 isn't meant to be run on a stock machine right? The minimum requirements are 4 MB fast ram, so clearly some things has to be disabled and Shell_VNC might be one of them (it's just a guess).

What is it you are trying to install that gives an error message? And how do you try to install it?
 

Offline marcfrick2112

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 811
    • Show only replies by marcfrick2112
Re: Startup-Sequence issues
« Reply #6 on: July 19, 2009, 03:18:41 PM »
punkyclown: I'd also suggest having a look at your user-startup. I'm curious about the request for IMIMIM:  I've never heard of it....

A silly idea, do you have a virus checker going on your system? That IMIMIM: sounds a bit fishy to me...
---------------
Marc Frick
---------------
A1200T / \'060, 256MB, CD-R, OS3.9
A4000 w/ WarpEngine / 82MB , OS3.1
A4000 16MB, OS 3.9
A1200 , \'030 / 10MB
A1200 (stock)

CD32 :)

...And a very sick 4000T
 

Offline punkyclownTopic starter

  • Sr. Member
  • ****
  • Join Date: Feb 2002
  • Posts: 262
    • Show only replies by punkyclown
Re: Startup-Sequence issues
« Reply #7 on: July 19, 2009, 05:44:33 PM »
Sorry, I should have said I have an 8 Meg memory board in the trap door with FPU.  I think I will disengage my user startup and see what happens, thanks.