What the heck is going on? All I get is access denied.
On 6/18/24 22:23, philo wrote:
What the heck is going on? All I get is access denied.
Check the ownership and permissions of the file that is being used for
the image.
Make sure that it's writable by the user(s) that is (are) trying to use it.
Now that I have all my machines up & running it's time to play.
I was recently informed of a site where can access Xenix and I should be
able to play a Unix...text based game. https://www.pcjs.org/software/pcx86/sys/unix/sco/xenix/086/2.1.3/
All I have to do is put it on a floppy image.
I can create a floppy image by using "dd" or by using Virtual Box.
It is impossible to write to it.
What the heck is going on? All I get is access denied.
I Googled an saw a lot of people asking the same questions. Zero answers .
I can create a floppy image by using "dd" or by using Virtual Box.
It is impossible to write to it.
What the heck is going on? All I get is access denied.
On 19.06.2024 um 03:23 Uhr philo wrote:
I can create a floppy image by using "dd" or by using Virtual Box.
It is impossible to write to it.
What the heck is going on? All I get is access denied.
Run
ls -la <filename>
and post the content here.
OTOH if I use Virtual Box to make a floppy image, that is something I
can mount. The problem is , it's impossible to write to
On 6/20/24 13:58, philo wrote:
OTOH if I use Virtual Box to make a floppy image, that is something I
can mount. The problem is , it's impossible to write to
It seems to me like you may have multiple things working against you.
My experience has been that VirtualBox (along with some other
hypervisors) want to be able to understand what's on the disk (image). Meaning you can't just use them as a raw storage device holding
whatever. You need to use a file system that VirtualBox understands.
The next issue you'll likely run into is that the software inside of the
VM may not know how to work with that same format. -- I wouldn't bet a gas station cup of coffee that Xenix would understand a FAT-12 file
system used on DOS (compatible OS) floppy disks.
On 6/20/24 13:58, philo wrote:VirtualBox understands.
OTOH if I use Virtual Box to make a floppy image, that is something I can mount. The problem is , it's impossible to write to
It seems to me like you may have multiple things working against you.
My experience has been that VirtualBox (along with some other hypervisors) want to be able to understand what's on the disk (image). Meaning you can't just use them as a raw storage device holding whatever. You need to use a file system that
The next issue you'll likely run into is that the software inside of the VM may not know how to work with that same format. -- I wouldn't bet a gas station cup of coffee that Xenix would understand a FAT-12 file system used on DOS (compatible OS)floppy disks.
On 6/20/2024 3:08 PM, Grant Taylor wrote:can mount. The problem is , it's impossible to write to
On 6/20/24 13:58, philo wrote:
OTOH if I use Virtual Box to make a floppy image, that is something I
hypervisors) want to be able to understand what's on the disk (image).It seems to me like you may have multiple things working against you.
My experience has been that VirtualBox (along with some other
VM may not know how to work with that same format. -- I wouldn't bet a gas station cup of coffee that Xenix would understand a FAT-12 file system usedThe next issue you'll likely run into is that the software inside of the
VirtualBox.taking .img file
# Things that smell like floppy
guest ------ 34-pin floppy (physical floppy, 34 pin cable)
------ USB packet passthru to USB Mitsui floppy 1440K
------ virtual floppy controller, add virtual floppy drive,
$ Things that smell like USB sticks(can be accepted as a "stick")
guest ------ USB packet passthru to actual USB stick
------ virtual USB controller, add USB "disk", taking .vhd file
There are things in that list that do not support boot.
Xenix supports 720K floppy of some sort, plus there is
a Xenix file system. The "disktype" utility reports:
Regular file, size 720 KiB (737280 bytes)
XENIX file system (SysV variant), little-endian, 1 KiB blocks
When you prepare a floppy .img file and put a tarfile first,
followed by zeros, that's an emulation of a "tape". That's
what a tape would taste like.
Would an OS be crazy enough to probe every storage bus for
"tape behavior" ???
Back in the day, on SCSI bus, if you stuck something at
address "6" on a certain OS, it would get probed for tape behavior.
Do a rewind. Check the mode sense. That sort of thing.
For an OS to be probing a floppy that way, that's pretty weird.
It's unlikely that Xenix would know what FAT12 is. but
you never know.
Paul
"Paul" <[email protected]d> wrote in message news:v527ck$2ooer$[email protected]...
On 6/20/2024 3:08 PM, Grant Taylor wrote:can mount. The problem is , it's impossible to write to
On 6/20/24 13:58, philo wrote:
OTOH if I use Virtual Box to make a floppy image, that is something I
It seems to me like you may have multiple things working against you.
hypervisors) want to be able to understand what's on the disk (image). Meaning you can't just use them as a raw storage device holding whatever.My experience has been that VirtualBox (along with some other
You need to use a file system that VirtualBox understands.
VM may not know how to work with that same format. -- I wouldn't bet a gas station cup of coffee that Xenix would understand a FAT-12 file system used on DOS (compatible OS) floppy disks.The next issue you'll likely run into is that the software inside of the
VirtualBox.
# Things that smell like floppy
guest ------ 34-pin floppy (physical floppy, 34 pin cable)
------ USB packet passthru to USB Mitsui floppy 1440K
------ virtual floppy controller, add virtual floppy drive,taking .img file
$ Things that smell like USB sticks
guest ------ USB packet passthru to actual USB stick
------ virtual USB controller, add USB "disk", taking .vhd file(can be accepted as a "stick")
There are things in that list that do not support boot.
Xenix supports 720K floppy of some sort, plus there is
a Xenix file system. The "disktype" utility reports:
Regular file, size 720 KiB (737280 bytes)
XENIX file system (SysV variant), little-endian, 1 KiB blocks
When you prepare a floppy .img file and put a tarfile first,
followed by zeros, that's an emulation of a "tape". That's
what a tape would taste like.
Would an OS be crazy enough to probe every storage bus for
"tape behavior" ???
Back in the day, on SCSI bus, if you stuck something at
address "6" on a certain OS, it would get probed for tape behavior.
Do a rewind. Check the mode sense. That sort of thing.
For an OS to be probing a floppy that way, that's pretty weird.
It's unlikely that Xenix would know what FAT12 is. but
you never know.
Paul
Done setting up all my Linux machines.
Now testing out a Win98 P-1
On 6/20/2024 3:08 PM, Grant Taylor wrote:VirtualBox understands.
On 6/20/24 13:58, philo wrote:
OTOH if I use Virtual Box to make a floppy image, that is something I can mount. The problem is , it's impossible to write to
It seems to me like you may have multiple things working against you.
My experience has been that VirtualBox (along with some other hypervisors) want to be able to understand what's on the disk (image). Meaning you can't just use them as a raw storage device holding whatever.� You need to use a file system that
floppy disks.The next issue you'll likely run into is that the software inside of the VM may not know how to work with that same format.� --� I wouldn't bet a gas station cup of coffee that Xenix would understand a FAT-12 file system used on DOS (compatible OS)
VirtualBox.
# Things that smell like floppy
guest ------ 34-pin floppy (physical floppy, 34 pin cable)
------ USB packet passthru to USB Mitsui floppy 1440K
------ virtual floppy controller, add virtual floppy drive, taking .img file
$ Things that smell like USB sticks
guest ------ USB packet passthru to actual USB stick
------ virtual USB controller, add USB "disk", taking .vhd file (can be accepted as a "stick")
There are things in that list that do not support boot.
Xenix supports 720K floppy of some sort, plus there is
a Xenix file system. The "disktype" utility reports:
Regular file, size 720 KiB (737280 bytes)
XENIX file system (SysV variant), little-endian, 1 KiB blocks
When you prepare a floppy .img file and put a tarfile first,
followed by zeros, that's an emulation of a "tape". That's
what a tape would taste like.
Would an OS be crazy enough to probe every storage bus for
"tape behavior" ???
Back in the day, on SCSI bus, if you stuck something at
address "6" on a certain OS, it would get probed for tape behavior.
Do a rewind. Check the mode sense. That sort of thing.
For an OS to be probing a floppy that way, that's pretty weird.
It's unlikely that Xenix would know what FAT12 is. but
you never know.
Paul
On 6/20/2024 3:08 PM, Grant Taylor wrote:
On 6/20/24 13:58, philo wrote:There are things in that list that do not support boot.
OTOH if I use Virtual Box to make a floppy image, that is something I can mount. The problem is , it's impossible to write t
Back in the day, on SCSI bus, if you stuck something at
address "6" on a certain OS, it would get probed for tape behavior.
Do a rewind. Check the mode sense. That sort of thing.
For an OS to be probing a floppy that way, that's pretty weird.
It's unlikely that Xenix would know what FAT12 is. but
you never know.
Paul
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 716 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 56:51:04 |
| Calls: | 12,117 |
| Files: | 15,010 |
| Messages: | 6,518,672 |