Started by OffseT, 16:51, 24 January 21
0 Members and 1 Guest are viewing this topic.
Quote from: OffseT on 21:31, 08 October 21|NODE will mark the Nova node with a "!" if it is in use.
Quote from: zhulien on 23:28, 08 October 21I couldn't however change into any DSK files, always mount failed.
Quote from: zhulien on 22:12, 08 October 21[...] no real need for NOVA?
Quote from: zhulien on 22:12, 08 October 21Currently there are no HXC nodes right? To use the USB as a native USB stick - as per Symbos? Then we can have 3 mass storage devices on line, 4 if adding 2 HXC devices at once - not including Albireo (which I don't have yet).
Quote from: OffseT on 10:54, 09 October 21Maybe using auxiliairy MotherX4 power supply could also fix your issue.
Quote from: OffseT on 11:00, 09 October 21Which error is reported?Are your files actually detected as DSK files? (you can see it by using, using |LIBRARY)Also, only unzipped DSK from the Library are supported.
Quote from: zhulien on 15:42, 09 October 21Only 'Mount failed', no more info. The DSK images are not zipped or compressed. I was thinking initially i got the syntax wrong, still not totally sure. They do work with the standard M4 ROM.
Quote from: zhulien on 18:23, 10 October 21|library doesn't list anything
Quote from: zhulien on 07:41, 11 October 21thanks, I will try that. I actually wondered what the library folder was for, my my mind I was thinking that when I opened a library, it used that folder as a scratch area of some type. thanks
Quote from: GUNHED on 23:27, 13 October 21imho !C should be reserved for the RAM disc to be compatible to RDOS.
Quote from: zhulien on 19:37, 13 October 21What is your thoughts on introducing a |c which can be assigned to any logical device? I suspect it would be a lot less compatible than |a and |b? But... some devices ROMs for example RAM drives historically had |c or |m. Going further if |c could work reasonable well for most things, what about adding another bunch... or will it take away standard CPC RAM for the RSX registrations?The reasons as follows. The logical to physical behaviour works really really good in UniDOS, but 2 drives can be a bit of a pain if you only temporarily want to check the contents of somewhere (as an example) but continue your main work from one location, and play around in another.
Quote from: zhulien on 04:33, 14 October 21I partially agree, but... if no technical reason otherwise, a RAMDISC could just be another UniDOS node which can expose a physical device. The benefits of the UniDOS way would be... you could have the Doberton RAMDISC, DkTronics one, the 3.5mb separate Jarek one etc or any other arrangements that can be assigned to any UniDOS letters.
Quote from: zhulien on 04:38, 14 October 21In fact, i might have a go at making a RAMDISC, it might be easier to get working than the dropbox-like internet disc
Quote from: zhulien on 03:33, 16 October 21libraries work fine once i put them into the library folder.the only thing odd, DSK remains assigned to |b for example, but the library gets lost upon reboot
Page created in 0.089 seconds with 53 queries.