VSdrive issue - not mounting any virtual volumes

[eositis]

Having an issue with VSDRIVE not mounting any volumes from my macbook. Data transfers with ADTPro work just fine. Can list catalogs and burn new floppies from images. However, when I try to run vsdrive the macos app confirms vsdrive has connected and reports blocks read. But on the IIc, the drives do not get mounted. Bitsy.bye skips right over the s1 drives, showing my floppy emu, slot3 ram disk and that is all. Slot 6 is no longer available. When I boot directly into the vsdrive disk and run -vsdrive, running 'cat,s1' returns an I/O Error.

On the mac side, I have virtual.po and virtual2.po in the disks folder. I have tried swapping these out with other .dsk files by renaming them, but nothing changes. unavailable.

The macbook is running 14.5.7

Any suggestions would be appreciated.

[Jayrom3]

First : I must say love ADTPro. Being able to fetch a 30 years old clumsy 6502 prog from an old (luckily still readable) floppy, onto my PC to run it on an Apple II emulator was a real blast !

This being said, I have the exact same issue as described by eositis.

Running ADTPro server on a Windows 11 PC and client on a Apple 2c ROM 4x:

• ADTPRO-2.1.0.dsk runs perfectly, disk files are transfered, new disk written, etc.
• VDRIVE-2.1.0.dsk gives an I/O ERROR when I do cat,s1 or cat,s1,d2 after starting VDRIVE.

What I have tried so far:

• I have written VDRIVE on a new 3M floppy (a rarity), to evacuate any floppy bugs issues.
• To verify VDRIVE was talking to the server, I have deleted the Virtual.po and Virtual2.po files on the server. They are recreated by VDRIVE, as they should be. Still : I/O ERROR.

Any help or feedback running VDRIVE will be apreciated.

PS : meanwhile, there is this FTP proxy for Apple 2 that looks amazing : https://github.com/colinleroy/a2tools?tab=readme-ov-file
But it is a bit more complicated to run than ADTPro.

[david-schmidt]

Question to either and both of you - when you first run -VSDRIVE, a message comes back like this:

VSDRIVE: DRIVES S1,D1/2 ON COMM SLOT 2

Those numbers are each significant - can you verify that's what you're seeing?

[Jayrom3]

Thank you for checking back on us so quickly!

• Yes, I get this exact same message, with the exact same numbers.

• More info about my server config:
  Windows 11
  DIN5 to USB cable with FTDI chipset
  Port COM5, Speed 19200 (imagewriter cable unckecked)

• Log extract after issuing 6 times "CAT,S1" command (same command each time, a +-2 seconds pause, then I/O Error message):
  27/01/26 08:16:03 Gui.actionPerformed() exit.
  27/01/26 08:17:11 CommsThread.commandLoop() Received data.
  27/01/26 08:17:11 CommsThread.commandLoop() Received a byte: C1
  27/01/26 08:17:11 CommsThread.commandLoop() Received wide protocol request.
  27/01/26 08:17:11 CommsThread.pullEnvelopeWide() entry.
  27/01/26 08:17:11 Waiting for byteslo...
  27/01/26 08:18:10 received byteslo: C1
  27/01/26 08:18:10 Waiting for byteshi...
  27/01/26 08:18:57 received byteshi: 85
  27/01/26 08:18:57 Waiting for command...
  27/01/26 08:19:25 received envelope command: C1
  27/01/26 08:19:25 Waiting for check byte...
  27/01/26 08:19:55 received checkbyte: 85
  27/01/26 08:19:55 calculated checkbyte: 44
  27/01/26 08:19:55 CommsThread.pullEnvelopeWide() received ill-formed envelope.
  27/01/26 08:19:55 CommsThread.pullEnvelopeWide() exit.
  27/01/26 08:19:55 CommsThread.dispatchCommand() entry.
  27/01/26 08:19:55 CommsThread.dispatchCommand() Received unknown command: 00
  27/01/26 08:19:55 CommsThread.pullPayloadWide() entry.
  27/01/26 08:19:55 CommsThread.dispatchCommand() exit.
  27/01/26 08:19:55 CommsThread.commandLoop() Waiting for command from Apple.
  27/01/26 08:20:35 CommsThread.commandLoop() Received data.
  27/01/26 08:20:35 CommsThread.commandLoop() Received a byte: C5
  27/01/26 08:20:35 CommsThread.commandLoop() Received virtual drive command.
  27/01/26 08:20:35 Waiting for command...
  27/01/26 08:22:35 CommsThread.pullEnvelope() aborting due to timeout.
  27/01/26 08:22:35 CommsThread.commandLoop() Waiting for command from Apple.

[david-schmidt]

Ok, envelopes aren't coming across correctly - there's no C1/85 command packet in the protocol (https://adtpro.com/protocol.html#ADTPro-Wide_Protocol_Packet_Formats). So do other chatty commands such as DIR and CD work correctly?

Port COM5, Speed 19200

This is unusual - I don't expect it's part of the problem because it should be resetting this internally to the fastest speed, but I don't recommend ever changing the bootstrapping/baud speed off of 9600. Best to leave that where it was set at the factory.

[Jayrom3]

• Envelopes. I confirm command like DIR and CD do work from ADTPro client. From VSDRIVE client I don't know how to test these commands. Do you have any guidelines for me? FWIW I have tried CATALOG,S1 and PREFIX,S1 after running -VSDRIVE.LOW and I got I/O Error too.
• Serial port test: I have changed port from COM5 to COM1, still no sucess.
• Force baud test: 9600 speed option is not available on my ADTPro client and ADTPro server. Only 19200 and 115200. I have edited ADTPro.properties to set CommPortSpeed=9600, without any sucess.
• Is ROM 4X the issue? I should be able to do some tests on a ROM 255 later this week.

[david-schmidt]

Maybe I'm mis-remembering about baud rate on the IIgs; it's OK to leave it at defaults, whatever those were.

I guess ROM 4X is a possibility, but I don't hold out high hopes - but if you could test on a ROM 255, that would be great. I've tested locally on a ROM 255 and VSDRIVE is working fine, so I don't expect a big regression or anything.

[eositis]

I will test tonight with a number of IIc rom versions. ElmarsSent from my Galaxy -------- Original message --------From: David Schmidt ***@***.***> Date: 1/27/26 09:57 (GMT-05:00) To: ADTPro/adtpro ***@***.***> Cc: Elmārs ***@***.***>, Author ***@***.***> Subject: Re: [ADTPro/adtpro] VSdrive issue - not mounting any virtual volumes (Issue #199) david-schmidt left a comment (ADTPro/adtpro#199) Maybe I'm mis-remembering about baud rate on the IIgs; it's OK to leave it at defaults, whatever those were. I guess ROM 4X is a possibility, but I don't hold out high hopes - but if you could test on a ROM 255, that would be great. I've tested locally on a ROM 255 and VSDRIVE is working fine, so I don't expect a big regression or anything. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[david-schmidt]

Here's a normal initiation of a CAT,S1 command as seen from the host log:

1/27/26, 10:26:05 AM CommsThread.commandLoop() Waiting for command from Apple.
1/27/26, 10:26:06 AM CommsThread.commandLoop() Received data.
1/27/26, 10:26:06 AM CommsThread.commandLoop() Received a byte: C5
1/27/26, 10:26:06 AM CommsThread.commandLoop() Received virtual drive command.
1/27/26, 10:26:06 AM Waiting for command...
1/27/26, 10:26:06 AM  received command: 03
1/27/26, 10:26:06 AM Waiting for blocklo...
1/27/26, 10:26:06 AM  received blocklo: 02
1/27/26, 10:26:06 AM Waiting for blockhi...
1/27/26, 10:26:06 AM  received blockhi: 00
1/27/26, 10:26:06 AM Waiting for checksum...
1/27/26, 10:26:06 AM  received checksum: C4 calculated checksum: C4
1/27/26, 10:26:06 AM Reading block 2
...

[eositis]

I have done some testing these last few days and am no longer able to replicate this issue. I see I raised this issue a bit over a year ago. Two primary changes I have made to the board. 1st is applied the IIc serial timing fix, that adds the crystal, cuts a few traces and adds a jumper. Second, I have replaced the original ROM255 with ROM4x. The machine model number is a2s4000.

@Jayrom3 can you confirm which ROM is installed in your machine, and if possible if it has the serial port fix?

[Jayrom3]

@eositis I confirm my initial tests have been done on an Apple 2c with a ROM4x (which fixes the serial port issue AFAIK).

I have just tried VDRIVE on a 2c with a 255 ROM and still have the same issue (CAT,S1 gives an I/O Error). While on this machine, ADTPro DIR and CD commands work fine too.

Maybe the problem comes from my Windows 11 installation. I might give it a go from a W10 VM later. Anyhow, I am very happy that ADTPro works for me and I resign I will do without VDRIVE for now.

[david-schmidt]

Could be the hardware (USB adapter) or could be the OS, as those things have been held constant as I understand your scenario so far. Testing with other adapters and machines would be really helpful in spotting a pattern.