Cosmos
Cosmos copied to clipboard
Unable to read files from Disk Image
Area of Cosmos - What area of Cosmos are we dealing with?
Filesystem
Expected Behaviour - What do you think that should happen?
Read anything from the Disk Image (Files, Directory Listings, etc)
Actual Behaviour - What unexpectedly happens?
FileNotFoundException happens
Reproduction - How did you get this error to appear?
Calling anything that requires 0:\
or 1:\
Version - Were you using the User Kit or Dev Kit? And what User Kit version or Dev Kit commit (Cosmos, IL2CPU, X#)?
Latest Version of the Dev Kit
Are you using a virtual machine or real hardware?
Virtual Machine
Sys.FileSystem.CosmosVFS fs = new Sys.FileSystem.CosmosVFS();
Sys.FileSystem.VFS.VFSManager.RegisterVFS(fs);
You are using this code, right?
Yup I am
Wait no I wasn't using the 2 line iirc (disgard this, i was on mobile and thought there was 3 lines of code lol)
Virtual Machine
Which one?
I was using Oracle's Virtualbox but iirc it happened in VMWare aswell
Yeah it does the same thing on VMWare
How are you adding the disks to vmware?
Just through the CD ROM disk with IDE (since this only happens with the cosmos iso and not hard drive imgs)
Just through the CD ROM disk with IDE (since this only happens with the cosmos iso and not hard drive imgs)
Cosmos automatically creates a pre-formatted fat32 vmdk for your VM, using a blank vmdk wont work
No I don't mean it like that If I put a file in isofiles it doesn't seem to read or even see if there's anything in the drive (that's why I said 1:) This was about the CD image and not a hard drive image, sorry about that
Oh yeah thats another thing, im experiencing it too, it just doesnt detects 1:
I see
Windows shows that the iso contains the files in isoFiles but Cosmos can't detect it for some unknown reason I'm running on the latest version but yeah this is confusing
@MishaTY Any idea what the issue could be?
I think this maybe the issue but i'm running a outdated version of cosmos right now so i'll try compiling a new version
Tried compiiling a new version and the issue seems to still be there
#2438 possible temporary fix