[N8VEM: 18622] Problem assigning drives under RomWBW 2.6 / UNA BIOS

[Edward Snider]

Hi everyone,

I'm trying out the new RomWBW 2.6 / UNA Bios on a SBCv2 and can't seem to
reassign drives to devices.
The mini PPIDE CF card and Dual SD are accessible as assigned during boot.

They are showing up as UNK1:0, UNK2:0, etc after being configured in the
UNA setup, not sure why.
I can read and write to them, they just don't seem to be recognized by
ASSIGN.COM.
I'm using the pre-buit UNA rom from the OutputUNA directory.

I must be missing something here, what is it?

Ed

<Loading Image...>

[John Coffman]

Ed,

Have you tried the UNA-CPM 2.2 from Will Sowerbutts yet?

Get the UNA binaries from the "UNA BIOS project" folder (UNA-BIOS.BIN,
FSFAT.BIN):


http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=UNA%20BIOS%20project
<http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=UNA%20BIOS%20project>

Then get the CPM.ROM and ROMDISK.ROM from the "UNA CPM" sub-folder:


http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=UNA%20CPM
<http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=UNA%20CPM>

The pre-built 512K ROM is in the zip files, or you can concatenate the
pieces yourself. Will has an extensive README in the zip file. The
UNA-CPM 2.2 and the UNA-BIOS grew up together, and possibly have more of
the kinks shaken out.

UNA Flash ROMs may be updated in-circuit from a FAT16 file system on the
SD or IDE cards.

--John

Post by Edward Snider
Hi everyone,
I'm trying out the new RomWBW 2.6 / UNA Bios on a SBCv2 and can't seem
to reassign drives to devices.
The mini PPIDE CF card and Dual SD are accessible as assigned during boot.
They are showing up as UNK1:0, UNK2:0, etc after being configured in
the UNA setup, not sure why.
I can read and write to them, they just don't seem to be recognized by
ASSIGN.COM.
I'm using the pre-buit UNA rom from the OutputUNA directory.
I must be missing something here, what is it?
Ed
<https://lh6.googleusercontent.com/-ChIYX8967kA/VAsZcH82E3I/AAAAAAAAAGE/UreefY37NbM/s1600/20140906_090342.jpg>
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

[Edward Snider]

Hi John,

I have been using one he sent me on the Mark IV that works very well,
and assigning slices is easy with REMAP.COM.

For now I went back to RomWBW 2.5 on the SBCv2, which is excellent,
especially with MAP.COM to help manage large, multi slice volumes.

I will definitely check out the readme and get more up to speed on UNA.
Being able to change configurations so easily is great.

Ed

Post by John Coffman
Ed,
Have you tried the UNA-CPM 2.2 from Will Sowerbutts yet?
Get the UNA binaries from the "UNA BIOS project" folder (UNA-BIOS.BIN,
http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=UNA%20BIOS%20project
http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=UNA%20CPM
The pre-built 512K ROM is in the zip files, or you can concatenate the
pieces yourself. Will has an extensive README in the zip file. The
UNA-CPM 2.2 and the UNA-BIOS grew up together, and possibly have more of
the kinks shaken out.
UNA Flash ROMs may be updated in-circuit from a FAT16 file system on the
SD or IDE cards.
--John
Hi everyone,
I'm trying out the new RomWBW 2.6 / UNA Bios on a SBCv2 and can't seem
to reassign drives to devices.
The mini PPIDE CF card and Dual SD are accessible as assigned during boot.
They are showing up as UNK1:0, UNK2:0, etc after being configured in the
UNA setup, not sure why.
I can read and write to them, they just don't seem to be recognized by
ASSIGN.COM.
I'm using the pre-buit UNA rom from the OutputUNA directory.
I must be missing something here, what is it?
Ed
<https://lh6.googleusercontent.com/-ChIYX8967kA/VAsZcH82E3I/AAAAAAAAAGE/UreefY37NbM/s1600/20140906_090342.jpg>
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

[Wayne Warthen]

Hi Ed,

I should be able to fix this tomorrow. I did all of my testing on Mark IV. Not sure why SBC would be different, but should be trivial to fix.

John,

Is it possible that different driver id's may be returned for SBC?

Thanks,

Wayne

[Wayne Warthen]

OK, yes, I see I am missing some UNA driver id's. Easy to fix and will
post it tomorrow.

--Wayne

Post by Wayne Warthen
Hi Ed,
I should be able to fix this tomorrow. I did all of my testing on Mark
IV. Not sure why SBC would be different, but should be trivial to fix.
John,
Is it possible that different driver id's may be returned for SBC?
Thanks,
Wayne

[Edward Snider]

Great!

Post by Wayne Warthen
OK, yes, I see I am missing some UNA driver id's. Easy to fix and will
post it tomorrow.
--Wayne

Post by Wayne Warthen
Hi Ed,
I should be able to fix this tomorrow. I did all of my testing on Mark
IV. Not sure why SBC would be different, but should be trivial to fix.
John,
Is it possible that different driver id's may be returned for SBC?
Thanks,
Wayne

[Wayne Warthen]

I have uploaded v2.6.1 of RomWBW to the Wiki. As far as I can tell it
fixes the issue. Seems to be working well for me on my SBC v2.

A few notes on this release:

- Note that the UNA build output is now in the Output Directory (not
OutputUNA) and the ROM image is called UNA_std.rom
- CP/M and ZSystem images are both integrated into ROM. You choose
which one you want at the boot loader menu.
- The ASSIGN command replaces old MAP command. Use ASSIGN /? for usage
- ASSIGN only allows swapping and reassignment of existing drive
letters. Does not allow adding/deleting drive letters (but will soon).
- The SYSCOPY command replaces the old SYSGEN command to make a disk
bootable. Use SYSCOPY /? for usage.
- Douglas' utilities have not been maintained and no longer work, so
they are not provided.
- There are a few places where the code assumes RAM and ROM disks will
be enabled. This will be improved soon, but would rarely be an issue in
normal use.

Thanks,

Wayne

Post by Edward Snider
Great!

Post by Wayne Warthen
OK, yes, I see I am missing some UNA driver id's. Easy to fix and will
post it tomorrow.
--Wayne

Post by Wayne Warthen
Hi Ed,
I should be able to fix this tomorrow. I did all of my testing on Mark
IV. Not sure why SBC would be different, but should be trivial to fix.
John,
Is it possible that different driver id's may be returned for SBC?
Thanks,
Wayne

[John Coffman]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
On 09/06/2014 08:53 PM, Wayne Warthen wrote:
<blockquote
cite="mid:a34d6ab7-b7c5-4e29-9871-c08a8ca19b90-/***@public.gmane.org"
type="cite">
<pre wrap="">Hi Ed,

I should be able to fix this tomorrow. I did all of my testing on Mark IV. Not sure why SBC would be different, but should be trivial to fix.

John,

Is it possible that different driver id's may be returned for SBC?
</pre>
</blockquote>
The SD card ID is the same -- 'Dual SDcard'.&nbsp; However, there are
multiple SDcard drivers:<br>
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Mark IV -- 'SDcard on CSIO' (same as N8-2312)<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; SBC v2 -- uses 'Dual SDcard' board on bus.<br>
<br>
The IDE slot will return a different ID:<br>
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Mark IV -- same driver as 'Dual IDE w/ Floppy' board.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; SBC v2 -- PPIDE driver -- same driver as 'DiskIO v3'.<br>
<br>
--John<br>
<br>
<br>
<blockquote
cite="mid:a34d6ab7-b7c5-4e29-9871-c08a8ca19b90-/***@public.gmane.org"
type="cite">
<pre wrap="">
Thanks,

Wayne

</pre>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br />
To post to this group, send email to <a href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br />
Visit this group at <a href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br />
For more options, visit <a href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br />