Unassign df0: in WB1.3

Gaula92 · 24 May 2011, 20:24

I know it can be easily done in WB 3.x and even 2.x, but... is it possible to unassing df0: in wb 1.3?

In case you're wondering why would I want to do souch a thing, it's because ISHAR still wants to save in DF0 when copied to HD. I have this problem solved in 3.x systems, but I would like to have it fixed for 1.x systems, too

gehtjanx · 24 May 2011, 20:32

unassing df0:???

Maybe you can assign another drive or folder to df0: but DF0: is always "there" (if no drive connected, DF0: ???" will appear except.

gehtjanx

TCD · 24 May 2011, 20:46

Er.. of course you can do that.

Code:

assign df0: dismount

thomas · 24 May 2011, 21:57

Quote:

Originally Posted by TheCyberDruid

Er.. of course you can do that.

Code:

assign df0: dismount

Did you actually read the question? He was asking about OS version 1.3. Dismount only exists in 2.0 and above.

TCD · 24 May 2011, 22:05

Quote:

Originally Posted by thomas

Did you actually read the question? He was asking about OS version 1.3. Dismount only exists in 2.0 and above.

Sorry, thought it was the same command in 1.3, since I've done it before. You're right it's 'assign df0: remove' in 1.3.

Gaula92 · 24 May 2011, 23:29

Thanks, thanks! Ishar now happily saving in HD, and running from HD on my 1.3 system!!

TCD · 24 May 2011, 23:43

Glad to hear it worked

I used it the same way a while back and assigning DF0 to HD works for some, but not all games

Gaula92 · 25 May 2011, 08:29

yeah... Moonstone resists: it works until the intro sequence ends, then asks for disk B, even if I copied disk B contents too.
Dungeon Master resists too.

thomas · 25 May 2011, 09:14

Add this to you startup-sequence:

assign <name of disk B>: <path where files from disk B are>

example:

assign Moonstone_disk_b: work:games/moonstone

(I'm just guessing, you need to use the real volume name of disk B!)

24 May 2011, 20:24	#1
Gaula92 Registered User Join Date: Aug 2008 Location: Spain Posts: 527	Unassign df0: in WB1.3 I know it can be easily done in WB 3.x and even 2.x, but... is it possible to unassing df0: in wb 1.3? In case you're wondering why would I want to do souch a thing, it's because ISHAR still wants to save in DF0 when copied to HD. I have this problem solved in 3.x systems, but I would like to have it fixed for 1.x systems, too

24 May 2011, 20:46	#3
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 32,044	Er.. of course you can do that. Code: assign df0: dismount

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Failing to set up a HD for wb1.3	Doc Mindie	support.WinUAE	11	23 September 2005 10:29
Problems running WB1.3 in WinUAE	The Rom Alien	support.WinUAE	7	15 December 2004 21:08
Old crunchers for A500/WB1.3?	Photon	Coders. General	21	03 December 2004 02:14
Hardfile for wb1.3/kickstart1.3 possible?	Amigalizard	support.WinUAE	5	10 December 2003 21:57
Creating a HDF with WB1.3	Exodus	support.WinUAE	39	11 February 2002 22:34

24 May 2011, 20:32	#2
gehtjanx Banned Join Date: Apr 2011 Location: Vienna / Austria Posts: 134	unassing df0:??? Maybe you can assign another drive or folder to df0: but DF0: is always "there" (if no drive connected, DF0: ???" will appear except. gehtjanx

24 May 2011, 23:29	#6
Gaula92 Registered User Join Date: Aug 2008 Location: Spain Posts: 527	Thanks, thanks! Ishar now happily saving in HD, and running from HD on my 1.3 system!!

24 May 2011, 23:43	#7
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 32,044	Glad to hear it worked I used it the same way a while back and assigning DF0 to HD works for some, but not all games

25 May 2011, 08:29	#8
Gaula92 Registered User Join Date: Aug 2008 Location: Spain Posts: 527	yeah... Moonstone resists: it works until the intro sequence ends, then asks for disk B, even if I copied disk B contents too. Dungeon Master resists too.

25 May 2011, 09:14	#9
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,035	Add this to you startup-sequence: assign <name of disk B>: <path where files from disk B are> example: assign Moonstone_disk_b: work:games/moonstone (I'm just guessing, you need to use the real volume name of disk B!)

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)