Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: AmigaFun on September 02, 2008, 10:39:42 AM
-
Hi all
Know this might be difficult to answer but will ask anyway.
Have now got my 40Gig HD partitioned via WinUAE into 2x900MB partitions and one 35GB partition. (formatted in FFS) I have copied the ClassicWB pack (ADV I think it was)and it works ok on WinUAE when booted from the hard disk, but when used in the A1500 it boots up, BUT when I try to open any program it locks up or Gurus with 8000 0004. I can use it if I hold down the LMB and use CLI to open the SysConfig, that seems ok, but not when the proper WB has loaded. I have deleted the MUI entries on the Startup Sequence in case that was the problem, but it still crashes.
When it's loaded the Chip Mem is 700,000 and Fast Mem is about 4,500,000 left.
Has anyone on here have any idea what I can try please?
Thanks you
-
I assume that you either have 3.x workbench,and you must have installed the correct patches to overcome the 4gigabyte limit of the amiga file system.
Did you use anything else on the winuae configuration?Something that might conflict with your current configuration on 1500 machine?
-
nikodr wrote:
I assume that you either have 3.x workbench,and you must have installed the correct patches to overcome the 4gigabyte limit of the amiga file system.
Did you use anything else on the winuae configuration?Something that might conflict with your current configuration on 1500 machine?
I have just copied all the files from the WinUAE Classic WB after that loaded up to the new partition on the 40Gig HD. I am hoping that has some sort of patch that sorts the 4GB limit. Put it this way, when the A1500 has booted up, and I open the 35GB partition it reports the size correctly.
As for any conflicts, not sure. It uses SCALOS but dont know how to disable that as it's not in the WBStartup draw.
-
Could you post your startup-sequence and user-startup files?There could be something to create conflict there.
Also i would advice you to temporary deactivate the 35giga partition and check to see wether you still have the crashes.I dont know what kind of patch is used in your case.
There are patches to overcome the 4giga limit of amiga filesystem.
Try this and tell us again.
-
Hi
Here is my Startup Sequence:
;ClassicWB Startup-Sequence 3.1
Wait 1
C:TestRMB
IF WARN
C:SetPatch QUIET
C:Version >NIL:
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
Assign >NIL: ENVARC: S:Env-Archive
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Execute >NIL: S:Minboot-Sequence
EndIF
C:TestLMB
IF WARN
C:SetPatch QUIET
C:Version >NIL:
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Assign >NIL: ENV: RAM:ENV
C:Assign >NIL: T: RAM:T
C:Assign >NIL: CLIPS: RAM:Clipboards
C:Execute >NIL: S:CLIboot-Sequence
EndIF
C:SetPatch QUIET
C:Version >NIL:
FailAt 21
IF EXISTS SYS:WBstartupD
C:Rename >NIL: SYS:WBStartup SYS:WBStartupM
C:Rename >NIL: SYS:WBStartupD SYS:WBStartup
EndIF
Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
IF EXISTS L:env-handler
C:MakeDir RAM:T RAM:Clipboards
L:env-handler
C:Copy >NIL: ENVARC:Sys/def_kick.info ENV:Sys/def_kick.info
ELSE
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Assign >NIL: ENV: RAM:ENV
EndIF
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
IF EXISTS C:BlazeWCP
C:BlazeWCP
EndIF
IF EXISTS SYS:Expansion/FBlit/FBlit
SYS:Expansion/FBlit/FBlit
SYS:Expansion/FBlit/FText
ELSE
C:Copy >NIL: SYS:Prefs/Presets/Newicons.prefs ENV:Newicons.prefs
EndIF
BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)
IF EXISTS DEVS:Monitors
IF EXISTS DEVS:Monitors/VGAOnly
DEVS:Monitors/VGAOnly
EndIF
C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
Execute T:M
C:Delete >NIL: T:M
EndIF
SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart
IF EXISTS C:IconBeFast
C:IconBeFast 0
EndIF
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
IF EXISTS S:User-Startup
Execute S:User-Startup
EndIF
Resident Execute REMOVE
Resident Assign REMOVE
C:LoadWB
EndCLI >NIL:
--------------------------------------------------------
Current User Start-up:
;ClassicWB User-Startup
C:Anticlick
Assign A-Games: DH1:Games
Assign A-Temp: DH1:Temp
Assign A-Programs: SYS:Programs
Assign A-MyFiles: DH1:MyFiles
Assign A-Demos: DH1:Demos
Assign LAUNCH: DH1:Files
Assign Scalos: SYS:Expansion/Scalos
Assign JPEGTMP: SYS:T
Assign AWEB_APL: A-Programs:AWeb_APL
-----------------------------------------------------
Original User Start-up:
;ClassicWB User-Startup
C:Anticlick
Assign A-Games: DH1:Games
Assign A-Temp: DH1:Temp
Assign A-Programs: SYS:Programs
Assign A-MyFiles: DH1:MyFiles
Assign A-Demos: DH1:Demos
Assign LAUNCH: DH1:Files
Assign Scalos: SYS:Expansion/Scalos
Assign JPEGTMP: SYS:T
Assign AWEB_APL: A-Programs:AWeb_APL
;BEGIN MUI
if exists Sys:Expansion/MUI
assign MUI: Sys:Expansion/MUI
if exists MUI:Libs
assign add LIBS: MUI:Libs
endif
if exists MUI:Locale
assign add LOCALE: MUI:Locale
endif
version >nil: exec.library 39
if not warn
if exists MUI:Docs
if exists HELP:dummy
endif
assign add HELP: MUI:Docs
endif
endif
endif
;END MUI
C:Mount KCON: from DEVS:KingCON-mountlist
C:Mount KRAW: from DEVS:KingCON-mountlist
SYS:System/Rexxmast >NIL:
C:xfdPatch >NIL:
Run >NIL: C:XpkMasterPrefs
C:CAPrefs >NIL:
----------------------------------------------
How do I deactivate the 35Gig partition?
Thank you
-
Push both mouse buttons when reset,and on the boot menu,disable the selected partition,then let it boot.Logically the selected partition won't be active at all.Does it still crash after that?
I am now looking at your startup-sequence file.
-
nikodr wrote:
Push both mouse buttons when reset,and on the boot menu,disable the selected partition,then let it boot.Logically the selected partition won't be active at all.Does it still crash after that?
I am now looking at your startup-sequence file.
Thank you, will try that.
I have deleted all refernces to BlazeWCP, and removed from Expansion FBlit. It seemed ok and I was able to install the Buddha s/w and then run a CUCD but when it was loading one of the draws it crashed again. For now its been taken apart to check for loose IC's etc.. Also plugging in spare GVP HD+8 SCSI card with 4MB ram.
Thank you for offering to check through that lot, appreiciated.
-
Doesn't scalos require an 020?
edit: never mind saw the specs of your 1500 in your sig