alternativer Filebrowser

Es gibt 54 Antworten in diesem Thema, welches 20.337 mal aufgerufen wurde. Der letzte Beitrag (7. Januar 2006 um 13:08) ist von Sylvester.

  • Bitte melde dich an, um diesen Link zu sehen. - all known bugs have been fixed, now onward to 0.5!

    I'm collecting database to identify different MMC/SD cards, if you want to participate then insert your card and wait for FAT scan to complete. Then press C= D to enter debugger, F7 until you get to memory address 8000. First line (starting with "8000") contains card specific data register (CSD), third line ("8020") is card identification register (CID). PM me contents of those two lines, together with card type and brand - don't forget possible manufacturer info on the back side of card.

  • Hi TNT!

    I have tested your new browser now, and I must say it´s so damn COOL. Especially the D64 and TAP feature is really great, man! Keep up this exceptional work! :)

    Have a nice day

    Oliver

  • Thank you both, it's always nice to hear someone else than me likes it too :)

    There is still problem with T64 loader, it only comes up with small (max. 32MB) cards. Those are hard to find anymore, but thankfully I got card image from Icon/Remember and dumping that to larger card allows me to debug it myself.

    (card->image is easiest with Bitte melde dich an, um diesen Link zu sehen., image-> card was done with Bitte melde dich an, um diesen Link zu sehen.. Remember to specify bs=64k for dd, otherwise it writes to card one byte at time which is extremely slow and possibly wears the Flash memory out)

  • Zitat

    Originally posted by tnt
    There is still problem with T64 loader, it only comes up with small (max. 32MB) cards.


    Bitte melde dich an, um diesen Link zu sehen. should fix any remaining problems with T64 loader. There was another bug which sometimes affected bigger cards as well, but that's fixed too.

  • Spam, spam, spam... :)

    Bitte melde dich an, um diesen Link zu sehen. which should fix T64 support for good. Total of three bugs there, I have to do better in the future.

  • Hello,
    First of all thank you for all the work you did on MMC64 plug-ins. This piece of hardware is probably the greatest I even bought. I own a secure digital card 512MB (brand: transcend). I have a problem: after transferring a large number of files, the card loses its directories. This is not a problem of MMC64, but I am reporting it, if someone knows a way to avoid this situation. I transfer the files via a 6in1 usb card reader and a commander running Debian 3.1 linux distribution in a Sun Sparc Ultra5.
    Secondly, many of the folders I use (with d64 & t64) have a lot of compilation disks with a text file that includes the contents of the whole disks. It could be nice to have a text viewer plug-in (into SYSTEM64 folder).
    Also, a joystick2/mouse arrow to browse into the directories could be a good idea.
    You can find my SD card data (lines 8000 and 8020) “photos” to the link: Bitte melde dich an, um diesen Link zu sehen.

    Best Regards,
    Sylvester

  • Zitat

    Originally posted by Sylvester
    I have a problem: after transferring a large number of files, the card loses its directories. This is not a problem of MMC64, but I am reporting it, if someone knows a way to avoid this situation.


    This sounds like a bug in FAT16 driver. You are not putting all files into root dir, are you? Root directory has limit of 512 entries, and long file names use multiple entries. Also, check the free space reported after directories disapper - that will tell if it's directory corruption (disk space disappears) or inadvertely triggered delete operation (you gain space for deleted files). Either way, better search Debian mailing lists to see if anyone else is having this problem.


    Zitat

    Also, a joystick2/mouse arrow to browse into the directories could be a good idea.


    Have you tried 1351 mouse in port 1? :) Support is lacking, I haven't used it myself for awhile after my breadbin C64 started dropping bytes when sprites were displayed. You can start PRGs with mouse, but you have to use <RETURN> if they are inside T64/D64. This will be fixed in the next version.


    Thanks for the card info.


    Edit: next version will have this in mmc.txt:

    Mouse:

    - LMB over filesize column, top/bottom
    scroll up/down

    - LMB over nonselected entry
    select

    - LMB over selected file/dir
    start prg/enter dir

  • Hi again,

    I have created folders of course for every category such as: SID, DEMOS, GAMES_PRG, GAMES_D64, etc... I have formatted the SD card to FAT-16. All my files are with long-filenames. To be honest, I have already the same experience with a CF card on MSX-2 from a friend's MSX. There is a cartridge like MMC64, that it's name is Sunrise-IDE-CF. And the story has: MSX uses FAT12 by default so 32MB is the maximum partition that the system can recognise at boot. In MSX scene there is a girl I think named OKEI that has made a patch to the MSXDOS2 (the dos of the msx) for FAT-16. So, I saw these kinds of problems in that CF, too. When I copy many disk image files (categorized by alphabetic folders for instance), there is a limit that over that, the cards lose their directories and files. That is why I wrote to my previous letter, that it is not a MMC64 problem. Please try to copy to an SD the "program files" folder from a windows system and you will see what will happen :smile:
    All files will be destroyed and you will see files like: %$#@%#^
    #^@

    My SD card has 230MB free at the moment (contains 5000-5.500 files). The problem is happening at about 300MB to my card. Perhaps fat16 designed for smaller number of files or every file has a hidden description or icon (like the .info on amiga) that has a size (that cannot be seen) and as I show 230 MB, the "true MBytes" are 460 !!

    So, after the copy fills the normal size of the SD, it does a cycle and writes from the beginning, destroying that way the MDB. I can assure you that this problem was the most common AHDI filesystem error on the Atari ST-TT-Falcon side.

    I am sure that it is not a Debian problem, as I tested in my work (windows XP SP2) with another SD card and a different card reader (8 in 1).

    I have not a 1351 mouse. I have tested Atari (ST)- Amiga (from A500)- PC Serial (pulled from an 8088) - MSX mouse ... but none of them works with Commodore :smile: So, I may buy one someday.
    But the joystick idea is nice, as we all have both joysticks in our Commodores!

    Also, I have to suggest you (as you are a programmer from outer space - really I like your job very much), first of all to inform Jens Schoenfeld about your versions of MMC64, to put them in his site, as I was very disappointed when I downloaded and installed the files he has at his MMC64 site :smile: Really, I was ready to through it from the window.

    Secondly I have to remind you if you can insert a test viewer plugin and a possible PDF viewer :smile:

    Note: when XE1541 is connected to a PC, the executables run but the system stops.
    When you shut-down the PC, the executables continue.

    The running of prg files with Final Cartridge 3 (no matter of the prg kbytes size) is instant. I mean it's so fast, like it was cartridge. Take care don't bother the specific code to that point :smile:

    We are waititng for the new version,
    Regards,
    Sylvester

  • I forget to write to my previous mail:

    a. the normal browser loads pictures and sids and then returns back to the menu, the "new browser" does not return and goes direct to basic.

    b. can commodore 128 & 128D use the 64kb more memory they have (for loading bigger fli interlaced pictures, sid, etc)?

    c. how is possible to run a game that has more than one D64 file ?

    regards,
    sylvester

  • Zitat

    Originally posted by Sylvester
    Please try to copy to an SD the "program files" folder from a windows system and you will see what will happen :smile:


    I have currently 37 MB free on my 512 MB card, no problems. Visual Studio alone takes 262 MB according to browser. Files have been written with Win2000Pro & noname 7-in-1 USB card reader/writer.

    The reason why file sizes don't add up with card/disk use is cluster size: on 512 MB card every file uses at least 8KB, so there's plenty of wasted space. I have routines to make browser understand multiple partitions (to lower the cluster size) but Windows is too stupid to use extra partitions on removable media.

    I might add support for Amiga mouse, but that's pretty low on my to-do list. At least I have to finish my plugin system first so browser can only load needed drivers - no need to waste memory for koalapad driver if it's not used :). Text plugin will be among the first ones when plugins work. I will publish plugin interface details so someone else can write the PDF plugin ;)

    Zitat

    inform Jens Schoenfeld about your versions of MMC64, to put them in his site


    Ok, I will do that but I'm not sure if he wants to add third-party software as that kind of implies support too.

    I will check the issue with XE1541, though I only have XA1541 at the moment.

    I have only tested MMC64 with RetroReplay this far, but I'm currently dumping Expert Cartridge disk (with Kratznagel's cool D64 writer) so I can test with it too.

    Answers to your second post:

    a) Browser loads anything loadable, check koala pictures with C= F and you see they load into $6000, then loader tries to start program with equivalent to SYS $6000. Same with SIDs, because of header they are loaded to $5352 and tried to run there. Until there is plugin support you can't view pictures or play SIDs. The latter is best left for BIOS anyway for compatibility.

    b) On C128 one could use VDC memory for some data, but for most of things that doesn't help much. Even IFLI doesn't take so much memory that there isn't room for loader so it's no worth the effort.

    c) Sasq is working on alternative BIOS which should help with multipart games, but if game uses disk turbo then it won't work with MMC64 without modifying the loader code inside the game. That's the problem with every mass storage device for C64.


    Darn, MMC64 and Trilogic Expert Cartridge don't like each other. TFC 3 works but TFC reset hangs C64. Freezer seems to work.

  • Hi, do you know where I can find Sasq ?

    Yes the support for Amiga mouse could be great idea. Alomsot any Commodore 8 bit user has an Amiga. You said "At least I have to finish my plugin system first so browser can only load needed drivers - no need to waste memory for koalapad driver if it's not used". That's why asked you for a routine that drops the plugins to the second 64Kb of the commodore 128/128D.

    I have already sent to the author of IrfanView (image viewer for Windows), probably the best for me, to support KOALA and ARTSTUDIO image filetypes. If he do it we will be able to transform a big number of jpg or gif or bmp from digital cameras to the KOA format. I have tested a lot of programs on this way and only X-RAY 64 worked well, under windows 2000. But it does only executables pictures. It crashes under the creation of pictures. This prg pictures running very very fast from MMC-64.

    Sylvester

  • Sasq hangs around in Lemon64 forum every now and then.

    C128 memory can't be used in C64 mode, and MMC64 forces C128 into C64 mode.

    Hackzoid of Siders is writing MMClib so it will be easier to write programs for MMC64. He has written koala slideshow which shows all picures in subdirectory.

  • Zitat

    Originally posted by Sylvester
    Note: when XE1541 is connected to a PC, the executables run but the system stops.
    When you shut-down the PC, the executables continue.


    No problem here with XA1541. I tried both with XA1541 connected directly to C64 and XA1541 connected to 1541 connected to C64.
    Did you try with program that tries to access 1541? It might be that XE1541 blocks IEC bus when PC is on, that would explain the behaviour you experienced.

  • Hi,
    I cannot find sasq anywhere on the internet. I will continue my searching.

    I executed a Demo from the MMC64, from "Triad" demo "daname". I saw the welcome screen of the demo and the commodore stopped there. The XE1541 was connected between the PC and the Commodore. When I turned-off the PC the demo started to run immediately. We repeated that both times, with other demos and we decided to pullout the cable!! The PC is an old Pentium 3 I think with windows 98 se.

    So, check the XA1541 under these conditions.

    Sylvester

  • Zitat

    Originally posted by Sylvester
    I cannot find sasq anywhere on the internet.


    Bitte melde dich an, um diesen Link zu sehen.


    Zitat

    I executed a Demo from the MMC64, from "Triad" demo "daname".


    It's tracmo, so you can't expect it to work with X-cable inserted. With XA1541 it works until it tries to load more and stays in the loader screen. Nothing to do with MMC64 nor my loader code.

  • Ok,
    The link for Sasq you gave does not work. Please check it again.
    As I think to buy the 512k expansion memory for commodore, for Geos,
    have you checked it with MMC ?
    Also, any partition creator for the MMC64 ? (from commodore side).
    I know windows can see only one partition (if you have more to a card) but you can move the files later from this partition to the "windows hidden" other partitions internally via the Commodore. I have seen a partitioning application to the MSX Sunrise IDE Cartridge. It works the way I described above (with Fat12 or Fat16).

    Sylvester

  • That link works when Lemon64 is up again. Alternatively you can google around for Sasq/DCS or look him up at Bitte melde dich an, um diesen Link zu sehen..

    I have no idea if MMC64 works with REU or not, as I don't have one. It does work with IDE64, although IDE64 looks very stupid pointing upwards, especially if it's in front of your monitor. REU will look equally stupid in that orientation, and it will block only third of screen as it's smaller.

    I have partitioning/format software for C64, but currently it only works with two specific card sizes (=both of my cards). It's not going to be released until I make it a bit more intelligent. It's better than Windows formatter as it can squeeze some more usable space from your card (like you needed that with 512MB card!) by using all sectors and allowing you to use single FAT table if you want.

  • Zitat

    Original von tnt
    I have no idea if MMC64 works with REU or not, as I don't have one. .

    It works with the REU, as I already tested it. Unfortunately, REU DMA on the MMC64 SPI Register is unstable, since the SPI transfer needs a little bit more than 1 CPU cycle to shift the data.

  • Zitat

    Originally posted by Oliver_AIt works with the REU, as I already tested it. Unfortunately, REU DMA on the MMC64 SPI Register is unstable, since the SPI transfer needs a little bit more than 1 CPU cycle to shift the data.


    I think DMA could still be used by swapping data between MMC64 and REU memory. I've heard from a reliable source ( :) ) that writing to MMC64 in read mode is NOP, and swapping takes two CPU cycles per byte.