| |
Mace
Registered: May 2002
Posts: 1799 |
How to run IDE64 programs in VICE?
In WinVICE, it is possible to attach a *.hdd file in the IDE64 settings menu.
IDE64 files in CSDb come without such a file, so I was wondering how I could start IDE64 stuff in (Win)VICE.
Do I need to put those file in a new *.hdd file and if so, how?
Can't be hard.. right?
[edit]
Oh, hang on... I just found this:
VICE_IDE64_HOWTO
----------------
Revision 2003-01-15
VICE information: http://viceteam.bei.t-online.de/
IDE64 information: http://ide64.come.to/ (http://www.volny.cz/dundera/)
How to enable IDE64 controller emulation in VICE
------------------------------------------------
Drive settings -> Disable true drive emulation
Attach a cartridge image -> Attach IDE64 interface image...
=> select IDE64 ROM file (available from http://ide64.come.to -> IDE64 firmware)
Attach a cartridge image -> Set cartridge as default
In IDE64 Setup (start by pressing '<-' 'RESTORE' {'~' 'Pg Up' on US keyboard})
-> standard setup -> Disable Floppy speeder
Load "format" tool (available from http://ide64.come.to -> Download) into VICE
(x64 format4.prg) and follow instruction on the screen
The IDE64 harddrive is created in current directory path as file 'ide.hdd'
After the format is finished, the IDE64 harddrive is ready for use.
More information available at http://ide64.come.to/ -> Manual
----------------------------------- |
|
... 5 posts hidden. Click here to view all posts....
|
| |
mstram
Account closed
Registered: Dec 2013
Posts: 112 |
I've tried both IDEDOS 0.90 and 0.91, with Vice 2.45 / 2.4.16
How do I get the setup / "Direct Write" setting to "stick" ?
After changing the setting, then either resetting the emulator or running a program with file/autostart, the direct write reverts to disabled.
I guess the workaround is to just use the sample ide.hdd file and make copies of it. |
| |
soci
Registered: Sep 2003
Posts: 479 |
Quoting mstramHow do I get the setup / "Direct Write" setting to "stick" ?
After changing the setting, then either resetting the emulator or running a program with file/autostart, the direct write reverts to disabled.
That's the only thing which is non-permanent, by design. Once you've formatted the disk you don't need it.
Normally what you do is to load cfsfdisk, then go to setup, enable direct write, exit setup, run cfsdisk. No reset in between. |
| |
soci
Registered: Sep 2003
Posts: 479 |
Quoting MaceNow how do I get those files on the virtual HDD?
Fastest is to mount the image file with fusecfs. (Linux, BSD, etc.)
http://singularcrew.hu/idedos/fusecfs-1.8.2.tar.bz2
You can also create an ISO file with all the stuff and attach it. VICE will emulate a DVD drive and you can access the files inside the image with IDEDOS. (do not disable the Joilet extension or else filenames might be short)
Alternatively you can enable the USB server option (needs recent VICE) with an emulated V4.1 cartridge. At the same time start ideserv with "-m vice" option.
This will give you an USB pclink connection and you can copy stuff from/to the exported directory just like on a real C64.
http://singularcrew.hu/idedos/ideserv-0.29c-20150214.zip
If you use 0.91 then you don't even need to copy stuff to the HDD except in very exceptional cases as the protocol supports seeking over PCLink. (this is not available with 0.90) |
| |
mstram
Account closed
Registered: Dec 2013
Posts: 112 |
When is the ide.hdd file created ?
I followed the instructions in the VICE_IDE64_HOWTO, but the file was not created. |
| |
soci
Registered: Sep 2003
Posts: 479 |
A newer version of the howto is here:
http://ide64.org/vice_ide64_howto_rev2.txt
However the image file is not created any more in newer VICE versions.
There are many possibilities to create an image file.
You can use "dd if=/dev/zero of=ide.cfa count={somenumber}". Or "qemu-img create ide.cfa 100M". Or "truncate -s {size} ide.cfa". Or use a dumped raw image of some drive.
A somewhat less professional way is to take some big file (e.g. a video) and make a copy named "ide.cfa".
In all cases you need to format it at the end anyway ;)
There's one important thing. The current emulation does not go beyond 2Gb, so do not use a huge image file. |
| |
Grue
Registered: Dec 2001
Posts: 161 |
Quote:There's one important thing. The current emulation does not go beyond 2Gb, so do not use a huge image file.
This is a real pity, please come into 21st century and remove this limitation please! |
| |
soci
Registered: Sep 2003
Posts: 479 |
r29352 adds large file support. Works on Linux, possibly on some of the other ports too. |
| |
Grue
Registered: Dec 2001
Posts: 161 |
Downloaded latest build marked r29352 from http://vice.pokefinder.org/ and large images wont work on windows it seems :(
' |
| |
iAN CooG
Registered: May 2002
Posts: 3186 |
must be built with a compiler that supports fseeko() and ftello(), else normal fseek()/ftell() functions are used as before, leading to the same "problem". In other words, must be built with a 64bit compiler that supports such functions. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11350 |
yeah nightlies use mingw32. better find someone to provide 64bit builds =P |
| Previous - 1 | 2 - Next |
