Jump to content

OX.

Members
  • Content Count

    532
  • Joined

  • Last visited

Posts posted by OX.


  1. Here's the output from the debugger screen - Initializing AMS mode 2, size 1024k

    Loading file from resource: Type D, Bank 0, Address 0x1100, Length 0x01A0

    Loading file from resource: Type S, Bank 0, Address 0x0000, Length 0x8000

    Loading file from resource: Type P, Bank 0, Address 0x0000, Length 0xF800

    Loading file from resource: Type G, Bank -1, Address 0x0000, Length 0x6000

    Loading file from resource: Type C, Bank -1, Address 0x0000, Length 0x2000

    Loading file (C:\GameBase\TI99-4Av2\system\phm3026c.bin) from disk: Type C, Bank 0, Address 0x6000, Length 0x2000

    Loading file (C:\GameBase\TI99-4Av2\system\phm3026d.bin) from disk: Type X, Bank 0, Address 0x6000, Length 0x2000

    Loading file (C:\GameBase\TI99-4Av2\system\phm3026g.bin) from disk: Type G, Bank 0, Address 0x6000, Length 0x8000

    Loading file from resource: Type K, Bank 0, Address 0x0000, Length 0x0000

    Starting Sound

    Sample rate: 22050hz, Buffer size: 44160 bytes

    Starting Disk

    Starting Video

    Video Thread began...

    Starting video loop

    Client rect now 1088 x 832

    Timer thread began...

    Speech Buffer thread began...

    CPU thread began...

    Starting Window management

    Setting top of VRAM to >37D7 (3 files)

    Loading to VDP >096F DSK1.LOAD on drive type Image

    Can't find file LOAD on c:\gbgame\0\cug006.dsk.

    Setting file error 7 on file buffer 36

    Opening DSK1.LOAD on drive type Image

    PAB requested file type is IV254

    Allocating file buffer 0

    Can't find file LOAD on c:\gbgame\0\cug006.dsk.

    Releasing file buffer 18

    Setting file error 7 on file buffer 38

    Loading to VDP >096F DSK1.MINE on drive type Image

    loading 0x2E69 bytes

     

    which is followed by "I/O error 50" on screen.

     

    disk "CUG006" is attached, XB used to load using RUN"DSK1.MINE".

    CUG006.ZIP


  2. Hi Tursi, apologies for reporting this so late but it seems a bug has crept in reading (I think) pc99 disk images since version 363, only just noticed when running "The Haunted Mine" in Gamebase, in 363 and 364 it simply can't see the file whereas in 362 it still works fine.


  3. Download link for non UG members - http://www.sendspace.com/file/ojgnta

     

    Just unzip the archive to C:\ so that the path structure remains the same, apart from the gamebase install files there's nothing else to install it's all ready to go this time.

     

    Install the main gamebase install from here - http://sourceforge.n.../gamebase/v1.3/ to "C:\Gamebase"

     

    Any gamebase project that is copied in the that Gamebase folder will automatically be detected and able to run.

     

    You might want to make a shortcut of the main gamebase.exe to your desktop (the joystick icon)

     

    OX.

    • Like 3

  4. In Gamebase TI99 there are a few ex-cassette only games that have transfered to disk and have to be loaded using this technique as without the disk controller attached cassette only games have a little extra memory available that the disk controller would otherwise use :-

    Use Mini Memory module + expanded memory

    Select TI BASIC

    CALL INIT

    CALL FILES(1)

    OLD DSK1.[program] (Replace with OLD CS1)

    SAVE EXPMEM2

    CALL LOAD(-31888,63,255)

    NEW

    OLD EXPMEM2

    RUN (Replace with SAVE DSK1.[program])

     

    You could try using this but save it to disk instead of running the program.


  5. H-m-m---I'm using MESS v147 with QMC2 to start it. The disk images shouldn't matter, i.e., if they work on one version, they should work on any other. What device driver are you using for the floppies? I'm using the Myarc HFDC.

     

    ...lee

     

    What is QMC2? I'm using also using the myarc hfdc floppy driver, only thing I can think that is different is the version of MESS (140) and possibly the E/A cart image.


  6. Right now I'm having a little trouble with MESS; but, trying it on Classic99, I see that DISK_HI is 90. It should be 180 for two 90KB disks. IIRC Classic99 does not use a regular TI DSR for disk emulating disk access. It works on Classic99, but shouldn't because attempting to load beyond screen 89 should fail with DISK_HI containing 90. Once you load TI Forth, type the following to change DISK_HI to 180:

     

    180 DISK_HI !

    91 LOAD

     

    I can't guarantee this is the problem because I can't check it until I get MESS working for me again. :(

     

    ..lee

     

    It made no difference Lee, I'm using MESS 140.


  7. Nice work Walid, got it working in Classic99 but your TI Forth disk image does'nt want to play in MESS, tried it with a version of TI Forth I already had and it seems to just lock up after the 91 load command, yet still works fine in Classic99, any ideas?

×
×
  • Create New...