The thing with Quill needing mdv2_

[Chr$]

In the past the fact that Quill needs mdv2_ for the def_tmp file has been a hindrance on a couple of machines without a working mdv2_! You simply can't get any further and Quill will not load.

I worked out today that it only attempts to access mdv2_ when tk2 is present in ROM.

Out of interest, why is that? Is there a way of getting Quill to work with just access to mdv1_ and tk2?

[NormanDunbar]

If you have tk2, you have ram_ drives. Can you format ram2_size_of_mdv and format ram1_mdv1 (or however it works to image copy mdv1 to ram1) and then mdv_use ram_ -- would that work?

Cheers,
Norm.

[ones' complement]

I worked out today that it only attempts to access mdv2_ when tk2 is present in ROM.

Probably because its TK2 DATA_USE default? (DLIST to show)

[Chr$]

I worked out today that it only attempts to access mdv2_ when tk2 is present in ROM.

Probably because its TK2 DATA_USE default? (DLIST to show)

Aha, yes, I think you're right there. I'll try to remember that data_use is default mdv2_, useful tip that.

[bwinkel67]

I thought the config program lets you remap Quill's devices? Couldn't you just map everything to mdv1_?

I've modified the config program so I can map everything to higher mdv's for vDrive (i.e. change line 44 EXIT dlp). I don't usually run TK2 but am now curious if microdrive 2 spins up if I use Quill from mdv5_.

[Chr$]

That works, in fact better than data_use seems to. For some reason some of my Quill images are missing the config_bas file.