• Please review our updated Terms and Rules here

Bad disk image?

There is great news. The NABU disk images do NOT work on my NABU floppy drives. What both you guys ( @Chuck(G) and @durgadas311 ) figured out was correct for those disk images but that apparently is NOT the format for the NABU system I have, and I discovered I have Dave Dunfield's actual NABU system.

With the help of the recent NABU Network recreation software, I can access my disk drive and there are CP/M utilities in the menu. However, I am accessing it with a Rev A firmware as opposed the a Rev B firmware that provides a boot option for CP/M. I definitely know the original images do not work on my NABU drive either booting or trying to do a directory in the CP/M tools that are part of the Nabu Network. This is what I see when I try to access the CP/M boot disk that the image was created from (and checked with 22Disk):

NabuCPMDiskDir (Medium).JPG

I formatted a floppy in the Disk Utilities within NABU Network:

NABUFormat(Medium).JPG

I used NABU Basic to add a coupleof one line BASIC test files and then did an ImageDisk and this is what was displayed.
NABUImageDisk (Medium).JPG

The disk image NABUFLPY.IMD and a full binary dump NABUFLPY.DMP are in https://vintagecomputer.ca/files/Nabu/disk_images/

I am currently tryingto use this 22Disk definition. It works on the disk images just fine but not on the formatted diskette.

BEGIN NABU Nabu PC CP/M 3.0 SSDD 5.25"
DENSITY MFM,LOW
CYLINDERS 40
SKEW 1
SIDES 1
SECTORS 5,1024
SIDE1 0 1,3,5,2,4
BSH 3 BLM 7 EXM 0 DSM 195 DRM 95 AL0 11100000b AL1 0 OFS 1
END

Would anyone be willing to help provide a new definition?

I also have a question on how I might get the boot track off of the NABUPER1.IMD disk (because I think that works) and write it to the new formatted NABU disk. What tool is best for that?

Thank you.
 
Does the NABU BASIC have a FILES command ? If you insert the CP/M disk on it and try to list its contents ? Of course I would advise to try to work with a copy or at least a write protected disk.
 
There is a "Disk Utilities" option that has CP/M disk utilities. I did a DIRECTORY on the old Nabu disk images with that but... first FILES is a good diskette I formatted and wrote to. seond FILES is the Nabu CP/M boot disk.

Let's finish the discussion in the other thread please.

BASICFiles (Medium).JPG
 
i wonder if it will work on double sided drive as its asking for single sided? and the head select line is there.?
 
The 1797 does handle dual sided and I did try it at one time but, of course, it would not work because of the images. Turns out both of my drives were good too. I could not use one of them on a PC. That was weird.
 
But the drives are shuggart right ? How can you use them unmodified on the PC ? Wasn't the hard setting for the head / side ?
 
Second we are assuming the disk geometry for the BASIC NABU 4K is the same for the CP/M NABU Dev 8K. They could be different (made by different teams how knows ?)
 
you should be able to hookup a double sided drive to the nabu if it give the option to format it. the control line is there
 
One interesting test: try creating more than 32 files. See how the directory goes on BASIC NABU. Someone has reported the nabu images had weird 32 entries only.
 
I'm having trouble figuring out what's being asked here. Is it a different NABU disk image? If so, which of the above discussed ones is it?
Maybe I'm just dense this morning, but the chatter has me confused.
 
Thank you @Chuck(G).

Through the Nabu Network recreation software and visual CP/M tools within it, I was able to format a floppy on the NABU and write/read a couple of files to/from it. The format appears to be different because the previous 22Disk definition (below) is not valid. I cannot read the files on a DOS computer with 22Disk. All possible information I know is in the screenshots above.

The newly formatted disk image NABUFLPY.IMD and a full binary dump NABUFLPY.DMP are in https://vintagecomputer.ca/files/Nabu/disk_images/

Below is the definition for the old images that we originally worked on. Those previous disk images would NOT work on the NABU PC. I always thought I had a hardware failure but this newly published software allows the floppies to work and therefore, I could format a floppy and image it with ImageDisk.

BEGIN NABU Nabu PC CP/M 3.0 SSDD 5.25"
DENSITY MFM,LOW
CYLINDERS 40
SKEW 1
SIDES 1
SECTORS 5,1024
SIDE1 0 1,3,5,2,4
BSH 3 BLM 7 EXM 0 DSM 195 DRM 95 AL0 11100000b AL1 0 OFS 1
END

While the newly formatted disk is still SSDD with 40 cylinders and 5 x 1024 (there is a picture of the format above), there is something slightly off. If you could see what the difference might be, I would really appreciate it.
 
I can guess at the format, but a nearly-full disk image would be very helpful. Just put a variety of files on it and then post the IMD file. One short file leaves a lot of room for error.
 
Chuck(G) said:
I can guess at the format, but a nearly-full disk image would be very helpful. Just put a variety of files on it and then post the IMD file. One short file leaves a lot of room for error.
Click to expand...
I have 41 short files on a floppy (same oneline BASIC files). Is that okay?

Let's see if I can find an editor.
 
Okay, I will take my image PC apart and the Nabu drive apart and use the original floppies to make images once I get a decent file size. I can then make multiple copies. Might take me a bit. I just want to rule out any possible issues.
 
I have not been able to make a copy (via disk imaging and restoring) of a newly formatted NABU diskette yet, unfortunately. There is a backup utility within the NABU system and I can make backups to different floppies and rear/write to them with no issues.

I tried ImageDisk on my normal duplication computer, tried with an original NABU disk drive and even tried with the Applesauce software and none of the recreated diskettes show a proper directory. ImageDisk has no issues imaging the disk and writing it however it just doesn't work. I am going to try using a DSDD drive on the NABU tomorrow and see if that will work because it looks like the NABU format can handle more than one drive type. I won't know for sure until I try. If it comes to it, I'll go down the Greaseweazle/Kryoflux road and see if I can do flux images with proper recreation. Definitely frustrating but I'll be at it tomorrow.
 
snuci,
If you take at the NABUPER1.IMD file and process it with the IMD utilities IMDA and IMDU,
you can extract the NABUPER1.RAW and NABUPER1.TXT files. (I use the a.BAT file
to do this in DOSBox on Debian Linux.)

Code: 
IMDA NABUPER1.IMD > NABUPER1.TXT
IMDA NABUPER2.IMD > NABUPER2.TXT
IMDA NABUPER3.IMD > NABUPER3.TXT

IMDU NABUPER1.IMD NABUPER1.RAW /B /E /D >> NABUPER1.TXT
IMDU NABUPER2.IMD NABUPER2.RAW /B /E /D >> NABUPER2.TXT
IMDU NABUPER3.IMD NABUPER3.RAW /B /E /D >> NABUPER3.TXT

Looking at the NABUPER1.TXT file I see the following:
Code: 
$ IMDA NABUPER1.IMD > NABUPER1.TXT

IMageDisk Analyzer 1.18 / Mar 12 2012
IMD 0.2:  2/08/2005 18:43:16

Nabu Personal Computer

Disk 1

CP/M User

Required cylinders: 40
Required heads    : 1
Data rate         : 250kbps
Est. maximum track: 5630 bytes

Possible drives/options to write NABUPER1.IMD :

 5.25" DD 40-track
   Double-step: OFF

 5.25" QD 80-track
   Double-step: ON

 5.25" HD 80-track
   Double-step: ON
   250 kbps -> 300 kbps

 3.5" DD 80-track   NOTE: *1
   Double-step: OFF

 3.5" HD 80-track   NOTE: *1
   Double-step: OFF

*1 40 track image will use only first 1/2 of 80-track drive.



$ IMDU NABUPER1.IMD NABUPER1.RAW /B /E /D >> NABUPER1.TXT

IMageDisk Utility 1.18 / Mar 07 2012
IMD 0.2:  2/08/2005 18:43:16

Nabu Personal Computer

Disk 1

CP/M User

Assuming 1:1 for Binary output
 0/0 250 kbps DD  5x1024
      1   2   3   4   5 
      D   D   D   D   D 
 1/0  D   D   DE5 D   DE5
 2/0  D   D   D   D   D 
 3/0  D   D   D   D   D 
 4/0  D   D   D   D   D 
 5/0  D   D   D   D   D 
 6/0  D   D   D   D   D 
 7/0  D   D   D   D   D 
 8/0  D   D   D   D   D 
 9/0  D   D   D   D   D 
10/0  D   D   D   D   D 
11/0  D   D   D   D   D 
12/0  D   D   D   D   D 
13/0  D   D   D   D   D 
14/0  D   D   D   D   D 
15/0  D   D   D   D   D 
16/0  D   D   D   D   D 
17/0  D   D   D   D   D 
18/0  D   D   D   D   D 
19/0  D   D   D   D   D 
20/0  D   D   D   D   D 
21/0  D   D   D   D   D 
22/0  D   D   D   D   D 
23/0  D   D   D   D   D 
24/0  D   D   D   D   D 
25/0  D   D   D   D   D 
26/0  D   D   D   D   D 
27/0  D   D   D   D   D 
28/0  D   D   D   D   D 
29/0  D   D   D   D   D 
30/0  D   D   D   D   D 
31/0  D   D   D   D   D 
32/0  D   D   D   D   D 
33/0  D   D   D   D   D 
34/0  D   D   D   D   D 
35/0  D   D   D   D   D 
36/0  D   D   D   D   D 
37/0  D   D   D   D   D 
38/0  D   D   D   D   D 
39/0  D   DE5 DE5 DE5 DE5
40 tracks(40/0), 200 sectors (6 Compressed)



#22DISK
BEGIN NAB1  Nabu PC - SSDD 5.25" 48 tpi - 1024 x 5
DENSITY MFM, LOW
CYLINDERS 40 SIDES 1 SECTORS 5,1024
SIDE1 0 1,3,5,2,4
BSH 3 BLM 7 EXM 0 DSM 194 DRM 95 AL0 0E0H AL1 0 OFS 1
END

#cpmtools definition
# NAB1  Nabu PC - SSDD 5.25" 48 tpi - 1024 x 5
diskdef nab1
  seclen 1024
  tracks 40
  sectrk 5
  blocksize 1024
  maxdir 96
  skew 2
  boottrk 1
  os 2.2
end

#libdsk definition
[nab1]
description = NAB1  Nabu PC - SSDD 5.25" 48 tpi - 1024 x 5
cylinders = 40
heads = 1
secsize = 1024
sectors = 5
secbase = 1
datarate = DD

#Flashfloppy/GOTEK definition
[nab1]
cyls = 40
heads = 1
secs = 5
interleave = 2
bps = 1024
id = 1
#rpm = 360
rpm = 300
rate = 250
mode = mfm
iam = no



$ cpmls -f nab1 -D NABUPER1.RAW
     Name    Bytes   Recs  Attr     update             create
------------ ------ ------ ---- -----------------  -----------------
BACKUP  .COM     4K     32   
CCP     .COM     4K     25   
CHECK   .COM     3K     19   
CLEAN   .COM     3K     18   
COPYSYS .COM     3K     17   
CPM3    .SYS    15K    120   
DATE    .COM     3K     22   
DEVICE  .COM     8K     58   
DIR     .COM    15K    114   
DUMP    .COM     1K      8   
ERASE   .COM     4K     29   
FORMAT  .COM     5K     34   
GET     .COM     7K     51   
HELP    .COM     7K     56   
HELP    .HLP    41K    325   
NABUSHOW.COM     3K     21   
PATCH   .COM     3K     19   
PIP     .COM     9K     68   
PUT     .COM     7K     55   
RENAME  .COM     3K     23   
SAVE    .COM     2K     14   
SET     .COM    11K     83   
SETDEF  .COM     4K     32   
SHOW    .COM     9K     66   
SUBMIT  .COM     6K     42   
TYPE    .COM     3K     24   
   26 Files occupying    183K,       9K Free.

Which makes the floppy 40 Tracks, Single Sided, 5 Sectors of 1024 bytes making the image 204,800 bytes.
This makes sense and gives a good directory listing with cpmtools using a skew of 2.

BUT, if you look at the NABUPER1.RAW Image and search the HEX bytes for the DPB that is encoded in the
file you will find the following at 0x3E80.

Code: 
Hexedit NABUPER1.RAW
00003E80   00 08 03 00  00 00 00 00  20 00 03 07  00 97 00 3F  ........ ......?
00003E90   00 C0 00 00  10 01 00 02  03 00 00 28  00 03 07 00  ...........(....
00003EA0   C0 00 3F 00  C0 00 00 10  01 00 02 03  00 00 02 03  ..?.............

0x20 0x00 Drive 0 = 32 Tracks
0x03 BSH
0x07 BLM
0x00 EXM
0x0097 DSM


0x28 0x00 Drive 1 = 40 Tracks
0x03 BSH
0x07 BLM
0x00 EXM
0xC000 DSM

SPT BSH BLM EXM DSM DRM AL0 AL1 CKS OFF
$0020 $03 $07 $00 $0097 $003F $C0 $00 $0010 $0001

SPT BSH BLM EXM DSM DRM AL0 AL1 CKS OFF
$0028 $03 $07 $00 $00C0 $003F $C0 $00 $0010 $0001

Larry
 
ldkraemer said:
Which makes the floppy 40 Tracks, Single Sided, 5 Sectors of 1024 bytes making the image 204,800 bytes.
This makes sense and gives a good directory listing with cpmtools using a skew of 2.

BUT, if you look at the NABUPER1.RAW Image and search the HEX bytes for the DPB that is encoded in the
file you will find the following at 0x3E80.

Code: 
Hexedit NABUPER1.RAW
00003E80   00 08 03 00  00 00 00 00  20 00 03 07  00 97 00 3F  ........ ......?
00003E90   00 C0 00 00  10 01 00 02  03 00 00 28  00 03 07 00  ...........(....
00003EA0   C0 00 3F 00  C0 00 00 10  01 00 02 03  00 00 02 03  ..?.............

0x20 0x00 Drive 0 = 32 Tracks
0x03 BSH
0x07 BLM
0x00 EXM
0x0097 DSM


0x28 0x00 Drive 1 = 40 Tracks
0x03 BSH
0x07 BLM
0x00 EXM
0xC000 DSM

SPT BSH BLM EXM DSM DRM AL0 AL1 CKS OFF
$0020 $03 $07 $00 $0097 $003F $C0 $00 $0010 $0001

SPT BSH BLM EXM DSM DRM AL0 AL1 CKS OFF
$0028 $03 $07 $00 $00C0 $003F $C0 $00 $0010 $0001
Click to expand...

So the disk image, if used in drive A would not work. Can I edit the NABPER1.RAW and change Drive 0 to the same DPB as Drive 1? Then use this image?
 
It appears I cannot do disk images with double-sided drives in the NABU either. In this particular case, I can work with the diskettes on the NABU with no issues. Two DSDD drives and I can read my SSDD diskettes without issue. Still cannot get a directory from the original NABUPER1 disk image.

I copied over a bunch of files from my single-sided floppies created on the NABU to a newly NABU formatted DSDD diskette and that works fine. When I image the disk with ImageDisk, write it back and try to read it in the NABU, there are no files. So I wrote a file to it and I see the single file in the directory.

On the imaged diskette, the original directory starts at 0x1400. This has all of the files that I could previously see on the original diskette. The new file that I can now see on the imaged diskette is in a directory starting at 0x7860. 0x1400 is not being read. It appears to be reading 0x7860 now.

I am going to go back to the original SSDD drives and see if something similar occurs.
 
You must log in or register to reply here.
Back
Top