开云体育

First post here, so hello to all. After a long time I started having fun with Apple Pascal 1.3 again and with some surprise I discovered what I believe to be a bug that I had never noticed in the past years. var n:integer; ...ord(odd(n))... returns n, it should instead return 0 for even n and 1 for odd n I have not found any documentation on the subject "on the net". Has the same thing happened to you with other versions/machines? Do you want to try and report your findings here? Thanks Marco

Hi, Does anyone know the whereabouts of the source code for a p-code interpreter to run the UCSD p-system on a Motorola 6800 machine by any chance? Dave

I'm trying to add hard drive support to TDI's 6502 implementation of version IV. I can see that the system attempts to access drives 0 to 4 with drives 0 and 1 being the floppies and drives 2-4 currently just giving failure on initialisation. Does anyone know what needs to be done to add hard drive support? Is it just a case of patching the disk drivers (e.g. drive 2 accesses go to the hard drive) or is there more to it? Thanks, Rob

I am attempting to boot the UCSD IV-3_system2 .IMA disk image on an IBM 5170 PC-AT emulator and get an undefined op code. It also seems to fail on my RM VX/2 (386 AT Clone). However, it would appear to work on the 5150 IBM PC emulator. I can boot the PSYS22 DOS hosted variant on both the emulator and on my VX/2. Any thoughts? Thanks Peter

I am looking for documentation of the format / layout of .IMG. .IMA, .IMAGE files. It would be nice to find an algorithm for unpacking these diskette image formats to a .VOL file. Even better would be a Pascal/Delphi program that does this. -- Dan D

I just finished implementing p-System IV.0 under RomWBW. This is a native EBIOS implementation and is working very nicely. It brings a robust p-System implementation to about a dozen popular hobbyist computer platforms. Anyway, I was not able to find distribution files for IV.1, only IV.0. Does anyone know if the media for SofTech Adaptable p-System IV.1 for Z80 is available anywhere? I have searched this group and everywhere else I am aware of. Thanks! Wayne

Does anybody know where I can get the BIOS and various driver sources for the IBM PC implementation of the P-System? It seems that there are 2 distinctly different flavours: a native older IBM-PC implementation and an MS-DOS hosted implementation. I a interested in both of them. Thanks Peter

MS-DOS Hosted P-system defines 2 disks as part of the distribution set: 1) PSYSTEM - PSYSTEM.VOL + PSYSTEM.COM 2) MISC - MISC,VOL + DRIVERS.VOL + 2WORD.VOL The fist volume is on Hanns Otten's site plus copy here under psys1 & 2 but the misc disk seems to be missing. Does anybody know where I can obtain a copy of the MISC disk? Thanks Peter

I have had a further look at the IV disk transfer utilities: SEND, RECEIVE, & REMTALK. althogh interesting they require a fairly full implementation of Volumes REMIN & REMOUT which many implementations lack. I will investigate further Peter

I have seen a reference in passing that where as the default for v II is to have an interleave and a skew, for IV interleave is 1:1, Skew is 0. Can anybody confirm this to be the case? Thanks Peter

I am trying to use DISKCHANGE.CODE to change the interleave and skew but with out success! Say I have a 1:1 Interleave, Skew 0 source disk in Volume #4: and wish to create an interleave 2, skew 8 copy in Volume #5: what are the values I pump into DISKCHANGE? 1) When disk change asks for the Drive interleave ratio what does it mean? Is it the ratio between the original format and the target format or if the drives have different physical performance? is this 2:1 or 1:1 (same drive types) 2) Source parameters: src drive #4: interleave 1 skew 0 3) Destination parameters: dst drive #5: interleave 2 skew 8 As a further check. If I have a source disk with 4:1 interleave, skew 6 and wish to end up with an interleave of 2:1 and a skew of 8 what are the parameters to DISKCHANGE drive interleave ratio 1:1 src drive interleave 4:1 skew 6:1 dst drive interleave 2:1 skew 8 I presume that interleave is the ratio between logical_128byte sectors and the idents on the sector headers. ie that the disk is formatted with sector headers increasing sequentially. In the past I always used 1:1 interleave, skew 0 and dealt with the performance by phycically formatting the tracks with non-sequential sector headers and included the skew skips between tracks so any OS only needed to request sequential sector numbers and the fancy work was dealt with in the low level format program. Thanks Peter

What are standard disk geometries for UCSD? I am aware of 8" 1 side x 77 T x 26 spt x 128 = 256256 bytes => 500-6 blocks 494 blocks interleave 2:1, Skew 6:1 OBJ volumes 8" disk / 3 volumes: 1 side x 25-1T x 26 spt x 128 = 79872 bytes => 156-6 blocks 150 Blocks Apple II 1 side x 35T x 16 spt x 256 = 143360 bytes => 280-6 blocks 274 Blocks interleave 2:1, Skew 6:1 IBM PC 5.25" 1 side x 40T x 8 spt x 512 = 163840 bytes => 320-6 blocks 314 Blocks interleave ? skew ? I might presume that there are versions based upon IBM 360 Kb and 720 Kb formats Any parameters? Peter

So to clarify: A UCSD .VOL is file is essentially a linear ARRAY[0..n-1] of UCSD_block, UCSD_block : ARRAY[0..511] of byte. Where n is determined by the size of the disk in blocks and the array only covers the part of the disk accessible by UCSD filesystem. Any sector packing to fit a UCSD_block is the responsibility of the BIOS, normally assumed that there are 128 byte logical sectors. so for Standard 8" IBM3740 FM singles density disk 77 Tracks [0..76] sectors have address marks set to head=0, Track number, and sector number within the track. adjacent sectors are not sequentially numbered, there is an interleave. Followed by a track to track skew. eg so if no physical interleave 1:1 and no skew 0 on disk [h0,T0, S1], [h0,T0, S2],[h0,T0, S3],[h0,T0, S4], [h0,T0, S5], ... [h0,T0, S26] [h0,T1, S1], [h0,T1, S2],[h0,T1, S3],[h0,T1, S4], [h0,T1, S5], ... [h0,T1, S26] ... [h0,T76, S1], [h0,T76, S2],[h0,T76, S3],[h0,T76, S4], [h0,T76, S5], ... [h0,T76, S26] So if no physical interleave: 2:1 logical interleave and logical skew 6. Read every other sector sequentially => takes 2 revolutions to read a track. sequential access would be via a logical to physical sector interleave lookup table: 1st revolution all odd sectors [h0,T0, S1], [h0,T0, S3],[h0,T0, S5],[h0,T0, S7], [h0,T0, S9], [h0,T0, S11], [h0,T0, S13],[h0,T0, S15],[h0,T0, S17], [h0,T0, S19],[h0,T0, S21], [h0,T0, S23],[h0,T0, S25] 2nd revolution all even sectors [h0,T0, S2], [h0,T0, S4],[h0,T0, S6],[h0,T0, S8], [h0,T0, S10], [h0,T0, S12], [h0,T0, S14],[h0,T0, S16],[h0,T0, S18], [h0,T0, S20],[h0,T0, S22], [h0,T0, S24],[h0,T0, S26] 3rd revolution all odd sectors starting from 7 skip 6 sectors for track to track skew [h0,T1, S7], [h0,T1, S9], [h0,T1, S11], [h0,T1, S13],[h0,T1, S15],[h0,T1, S17], [h0,T1, S19],[h0,T1, S21], [h0,T1, S23],[h0,T1, S25], [h0,T1, S1], [h0,T1, S3],[h0,T1, S5], 4nd revolution all even sectors [h0,T1, S8], [h0,T1, S10], [h0,T1, S12], [h0,T1, S14],[h0,T1, S16],[h0,T1, S18], [h0,T1, S20],[h0,T1, S22], [h0,T1, S24],[h0,T1, S26], [h0,T1, S2], [h0,T1, S4],[h0,T1, S6] 5th revolution all odd sectors starting from 13 [h0,T2, S13],[h0,T2, S15],[h0,T2, S17], [h0,T2, S19],[h0,T2, S21], [h0,T2, S23],[h0,T2, S25], [h0,T2, S1], [h0,T2, S3],[h0,T2, S5],[h0,T2, S7], [h0,T2, S9], [h0,T2, S11], 6th revolution all even sectors [h0,T2, S14],[h0,T2, S16],[h0,T2, S18], [h0,T2, S20],[h0,T2, S22], [h0,T2, S24],[h0,T2, S26], [h0,T2, S2], [h0,T2, S4],[h0,T2, S6] [h0,T2, S8], [h0,T2, S10], [h0,T2, S12], The same equivallent performance could also be achieved by not using a translation table to convert sector numbers but instead by arranging adjacent sectors on the disk to be labelled with the interleave and skew in the format pattern. This is a simpler BIOS but a more complex format utility. [h0,T0, S1], [h0,T0, s14],[h0,T0, S2],[h0,T0, S15], [h0,T0, S3],[h0,T0, S16], [h0,T0, S4],[h0,T0, S17], [h0,T0, S5],[h0,T0, S18], [h0,T0, S6],[h0,T0, S19], [h0,T0, S7],[h0,T0, S20], [h0,T0, S8],[h0,T0, S21], [h0,T0, S9],[h0,T0, S22], [h0,T0, S10],[h0,T0, S23], [h0,T0, S11],[h0,T0, S24], [h0,T0, S12],[h0,T0, S25], [h0,T0, S13], [h0,T0, S26] [h0,T1, S4],[h0,T1, S17], [h0,T1, S5],[h0,T1, S18], [h0,T1, S6],[h0,T1, S19], [h0,T1, S7],[h0,T1, S20], [h0,T1, S8],[h0,T1, S21], [h0,T1, S9],[h0,T1, S22], [h0,T1, S10],[h0,T1, S23], [h0,T1, S11],[h0,T1, S24], [h0,T1, S12],[h0,T1, S25], [h0,T1, S13], [h0,T1, S26], [h0,T1, s14],[h0,T0, S2],[h0,T1, S15], [h0,T0, S3],[h0,T1, S16],[h0,T0, S1], ... ...[h0,T76,S26] Peter

https://www.autometer.de/unix4fun/z80pack/ The z80 PACK UCSD PASCAL disks claim to be 494 blocks, However, the file is 256 KB and not understood by any of the programs I have they expect a 494 block disk to be 247 kb image of the disk blocks. (UCSD section only) Or 250 kb entire disk including track 0. Clearly this .DSK format also includes some additional header information. Where do I find the specification for it? Thanks Peter

I am trying to get the Z80-MBC2 UCSD Editor to work with either Putty or TeraTerm. However, the setup as supplied does not appear to correspond with what the terminal emulations expect. Is there a published version of SYSTEM.MISCINFO and GOTOXY for either of these terminals or a version for a VT100? Thanks Peter

Once upon a time, there was a CPMFILER available for the 8080 / Z80 P system to allow it to interchange files with CP/M systems. I thought that I had a copy but it does not appear to be on any of my disks. Any ideas where I can download it preferably including the sources. Thanks Peter

Hi, I am experimenting with UCSD IV on the Z80-MBC2. The MBC2 can boot a number of different operating systems from SD files: CP/M 2.2, CP/M 3, and UCSD IV amongst them. (https://hackaday.io/project/159973-z80-mbc2-a-4-ics-homebrew-z80-computer) However, I am running into a number of issues: 1) It uses a non -standard SD file format to emulate a number of 1.2 Mbyte disk drives ( up to 6, volumes #4, #5, #9, #10, #11. and #12). However, although CiderPress can transfer files into and out of a number of UCSD image formats, Z80-MBC2 is not amongst them. The Z80-MBC2 documentation suggests the use of CPMTOOLSGUI, whereas this works fine for CP/M files it has no understanding what so ever of UCSD files nor is there a CP/M to UCSD utility to transfer files between OSes on the MBC. Neither does it include either XMODEM nor KERMIT file transfer programs in the UCSD. Though there is a non-working Xmodem program in CP/M. In short there seems to be a decided lack of mechanisms to get software into / out of the system 2) The Serial & Disk i/o is emulated via a MEGA32 chip (an overgrown arduino chip, same processor core but with more i/o pins brought out). This does not seem to include support for either hardware RTS/CTS flow control nor XON/XOFF and is very slow (characters per second). It is easily over run by most modern PCs. For some reason the baudrate has been set at 115200, which works fine for character at a time but noway can it keep up with either TeraTerm nor Putty throughputs. Though Putty seems to have a much lower character per second rate and works better. Neither will work for transferring files: paste is far too fast, Xmodem (under CP/M) drops too many characters to synchronise. 3) The UCSD Editor as supplied does not appear to be set up correctly and there would appear to be no-way to send it an ETX to end an insert. CTRL/C is ignored nor do the cursor keys appear to work. In the absence of a working editor nor a means to transfer files into / out of the system it currently remains a curiosity. 4) It is missing BINDER so it is not possible to add a new GOTOXY to match your terminal. 5) It only appears to recognise its own variant of a 1.2 Mb virtual disk, it would not appear to be able to identify / work with any other disk sizes. On boot it pushes some very non-standard disk geometry onto the stack. Not sure how to implement mutiple disk types. 6) Despite the 8 MHz Z80 it seems to run rather slowly far slower than Research Machines 380Z UCSD II implementation. Not sure if this is the lack of disk optimisation or the Mega32 slowing down the Z80 CPU. Nor as fast as my Apple II UCSD II.1. Has anybody else experimented with it with more success? I would be grateful for any suggestions / ideas. Thanks Peter