First, thank you for replying to all my posts. I literally just discovered torrents and emulators this week haha. So i have no idea what words mean or what i'm doing. I do believe it's a PPC Mac, although i do not know what that means in comparison to an Intel Mac. I noted that in your requirements you have an Intel Mac, so. You also have ePSXe using a CrossOver Mac or Windows or a CrossOver Game. I'm not sure i have that either.
In any case, i tried running the game using the configuration you have displayed, but i just get a black screen. As for ff7, i went to that link you provided and i think i found what my problem is, although i do not know what a SegFault is. Unfortunately, the solution is as follows: '???' I'd appreciate any help you could offer. Also, i was wondering if you knew how to - well, i don't know what the word is - put, say, all the cds of a particular game on your computer so that you could run the game in the emulator without having to hold on to the discs. I'm not talking about getting them from the internet - i actually have the discs. Thanks a real lot, man.
I successfully made a live USB of the Kali Linux. When I boot from the USB it gives an option to install. I clicked on that option.
At one point it was detecting and mounting CD-ROM drives. As I have no CD-drive or any ROM-drive on my laptop, it gives an error Can't mount and detect CD-ROM drives. I tried the 'live something' option that takes me directly to Kali Linux and it loads successfully but I can't install it permanently.
Aug 26, 2013 - PBP and they play fabulously.i know that really does not help you. Same thing with.iso I think. You can check redump.org to see if your game is with copy. Whether the are.cue/.bin or.ccd/.img/.sub i compress the disk images into. Being able to handle PSX-Isos as smaller rom files and feeding.
I want to install it so I won't have to waste my time plugging and unplugging the USB. How to get past the CD-ROM detection and make the installation finish correctly? You could resolve the error by repeating the steps: Run the installer. Open a shell ( ALT + F2). Create the directory cdrom directly on the root of the file system: mkdir /cdrom Note: If you got problems making the directory /cdrom, disable the CD-rom player in BIOS or disconnect the cable Mount the USB as if it is a CD-ROM: mount -t vfat /dev/sdb1 /cdrom Where sdb1 is your USB device.
You could carry on installation now After executing mount -t vfat /dev/sdb1 /cdrom, cd into the /cdrom directory and do an ls to see if the files are there. Then press ALT- F1 to go back, continue and re-select 'detect CDROM' Source: and Another was: when the Window shows CDROM couldn't be mounted,. Unplug your USB from system and re insert it.
![Check Check](/uploads/1/2/5/3/125359796/867868512.png)
wait for mount/ detection (usb LED glow). Hit Continue You could do what I did. Hit escape, type install, hit enter, skip CD drive.
![All psx roms torrent All psx roms torrent](/uploads/1/2/5/3/125359796/719617934.jpg)
I tried all the answers here and more google results, but none worked. I eventually figured it out, the issue is the file format is not vfat, but iso9660. When you get the CDROM not found error follow these steps: Enter a shell ( CTRL+ Alt+ F2) Note: Kali told me to press ( Alt+ F2), but this didn't work Get a list of devices with blkid: # blkid /dev/sdc1: UUID='2018-04-12-12-04-16-00' LABEL='Kali Live' TYPE='iso9660' PARTUUID='81c5e086-01' Note: I have shortened my list to the relevant row. Also you can see the storage type is iso9660, not vfat Mount the Kali CD with the mount command: # mount -t iso9660 /dev/sdc1 /cdrom Check the contents of /cdrom are as expected: # ls /cdrom autorun.inf efi g2ldr.mbr md5sum.txt win32-loader.ini boot efi.img install pool debian firmware isolinux setup.exe dists g2ldr live tools Switch back to the installer ( CTRL+ Alt+ F5) Note: Kali told me to press ( Alt+ F1), but this didn't work.
I tried F1 through to F5 until I found the correct combination From the menu tell it to mount the CDROM, if asked choose /dev/sdc1 and /cdrom. I know we have already mounted the drive, but for some reason this step didn't work previously, but worked fine after following the previous steps. The install will now continue as normal.