. /../VNoctis virtualized Noctis IV.../ 12
ah didn't learn anything!
written by Selbio on Feb 01, 2010 23:45
That might still work, actually. Just run the commands in a terminal. mkfs.msdos might be something different, and -o loop might be different or unnecessary, but it should be the same idea.
yummy jam!
written by Jam on Feb 07, 2010 15:35
This seems to work:
$ hdiutil create -fs MS-DOS -sectors 2880 floppy
$ mv floppy.dmg floppy.img
You will need to format the floppy using DOS:
format A:
Then just use the 'copy' command to move files to the floppy image.
└> last changed by Jam on February 07, 2010 at 16:07
r'lyeh sweet r'lyeh
written by Neuzd on Feb 07, 2010 17:05
Jam said:
This seems to work:

$ hdiutil create -fs MS-DOS -sectors 2880 floppy
$ mv floppy.dmg floppy.img
You will need to format the floppy using DOS:

format A:

Then just use the 'copy' command to move files to the floppy image.
This is actually just half of the job, though.
Anyway, for what concerns OSX, I found that two way transfer is extremely easy.

So, formatting the floppy in DOS is the first step for anything you want to do.
After that, for reading/writing in the DOS environment simply use the usual DOS commands.
For reading/writing on OSX, the simpliest thing to do is renaming your floppy.img to .dmg every time you want to access its content.
Mount the .img on the desktop (double click it) and copy the files you want from the finder.

I find it a very little problem having to rename the file to .dmg for OSX and .img for DOS.
I find that I'm pretty an idiot not having noticed before that the .img mounts exactly the same of a .dmg, so there's no need to rename it every time : P

Interesting to note is that the zipped guide fits the floppy size : )
└> last changed by Neuzd on February 07, 2010 at 19:28
written by Cryoburner on Sep 25, 2010 13:19
I was taking a look at VNoctis again today, and after updating VirtualBox to the most recent version 3.2.8, there seems to be an incompatibility, as moving the mouse in FreeDOS, or once Noctis has started, causes the virtual machine to crash. I reinstalled the older 3.1.8, and the problem isn't present there. I didn't test any releases in between those two. Does anyone else encounter this issue with recent versions of VirtualBox?
doing pushups
written by Megagun on Sep 25, 2010 14:03
No problems here with Virtualbox OSE 3.2.8 under Arch Linux here (freshly downloaded VNoctis)
written by Cryoburner on Sep 25, 2010 15:16
It might be an issue that only appears in the Windows version, or possibly something related to certain mouse drivers. I'd be interested in knowing if anyone else running it in Windows encountered that problem.

Also, I should point out that you seem to have included a current.bin file for Noctis and NIV Plus. The problem with this is that when Noctis starts, it updates the amount of fuel based on how long you've been away. Since it's been a number of months since this was released, you end up starting with no fuel, which probably isn't very friendly to those trying out Noctis for the first time. : P
doing pushups
written by Megagun on Sep 28, 2010 17:54
I confirmed today that indeed 3.2.8 has some strange mouse issues in general, not just with VNoctis loaded. It looked as if they're attempting to have seamless mouse integration for OSes that don't support it, but failing horribly. I guess there's some setting somewhere that gets rid of that problem, but I didn't bother searching for it, myself.
ah didn't learn anything!
written by Selbio on Sep 28, 2010 19:24
Settings, System, uncheck "Enable absolute pointing device."
reading this thread
no members are reading this thread
. /../VNoctis virtualized Noctis IV.../ 12
24938, 12 queries, 0.070 s.this frame is part of the AnyNowhere network