WB3.1 no boot!

[JMoS]

Hello!
I got for my A1200 a KS3.1 and a WB3.1.
I wanted to install NDSPatch so as to be able to handle disk with size over 4GB.
I did a newbie mistake, not to create an image of this disk before applying the patch. Yes I know is a very bad practice!
But it is what it is, and I have to keep finding a solution
But once installed, during the 1st boot it has stalled on a library and since it froze on a "dark screen of the death"
While I have desactivated it from the startup-sequence what I can see is that it starts the boot sequence (activity led on) and few seconds later it keep displaying a dark screen and no more disk activity.
I can access the contents of the disk with the "no boot sequence".
I would like to know if I can reverse this situation as I was nearly
Any tips/help welcome
Thanks

[AMIGASYSTEM]

This should not have happened, are you sure you have not modified anything else?

To delete NSDPatch you have to do this:

- Delete or deactivate from the Startup-sequence the string
C:NSDPatch QUIET

- Delete
C:NSDPatch
DEVS:NSDPatch.cfg

[thomas]

NSDPatch does not give you access above 4GB if the device does not have this ability already. You can better exploit this ability with a suitable file system. NSDPatch has no advantage at all.

To find out where the boot process stalls you can boot without startup-sequence, then enter

set echo on
execute s:startup-sequence

or add

set echo on

to the beginning of startup-sequence.

[JMoS]

thanks!
I will then delete totally NSDPatch and add the echo on in my startup-sequence and will give you a feedback

[JMoS]

Ok I finally went thru...
Here is what I have done:
i) boot w/o startup-sequence
ii) remove any reference to NSDPatch from the script above
iii) remove C:NSDPatch & Devs:NSDPatch.cfg
iv) lauch the workbench : C:loadWB
Then it the black scrren is gone and a window AmigaDos appear and right away a requester window asking to close any drawer left open but as any drawer at this stage is open it stalled forever
Then click on CANCEL followed by a ^C

and TaDaaa!!!

it keeps booting...
Nothing has been lost only few prefs needed to be re-adjusted.

At the moment I have to keep invistegating why I still got this requester else I can say that it is working again.
Thanks for your help

[Jope]

If anything writes to the initial CLI, you will get the requester from iprefs. Adjust your startup-sequence to add nil: redirections and quiet arguments to suppress any text.