[How To] Use the Katana SDK on Windows 7

Discussion in 'Sega Dreamcast Development and Research' started by T_chan, Jan 30, 2010.

  1. T_chan

    T_chan Gutsy Member

    Joined:
    Apr 13, 2008
    Messages:
    448
    Likes Received:
    51
    As promised, a complete tutorial on how to run the Katana SDK with your favorite devkit on Windows 7...
    Maybe an administrator can make this sticky ? (hmmm... on the other hand, how many people are actually interested in this tutorial... ?)

    Why this tutorial ?
    - because ater a clean install, Windows7 cannot communicate with the Katana devkit
    - because wnaspi32.dll is not supported on Windows7
    - because the current version of FrogAspi does not work with the Katana devkit

    [New - November 2016: How to use the Katana SDK on Linux]

    [New - July 2016: if your motherboard only has PCIe slots, no PCI slot, also have a look at this thread: How to connect the HKT-01 devkit without pci slot]

    [New - 2015: To replace the SCSI harddisk, have a look at this thread: Recommended hard drive for katana dev unit]

    PREREQUISITES:
    ==============
    - the Katana devkit hardware correctly set-up to run (ie, the cables & jumpers, and the SCSI terminator)
    - Windows 7. This was tested with the 64bits version only... (who cares about the 32bits version anyway ?)
    - the Katana SDK installed. Tested with SDK R11 only.
    When installing the SDK, it will tell you to:
    - install updated ASPI drivers at the beginning of the install -> just ignore & continue
    - reflash the devkit at the end of the installation -> ignore this
    - before starting this installation, be sure to do the actual boot sequence for the devkit:
    first boot the devkit, wait a few seconds, then boot your pc
    check that the pc mentions the GD-M & the DA during the boot process of the scsi card


    WARNINGS !!!!!
    ==============
    - MekugiAspi is still in early development phase, so
    - USE AT YOUR OWN RISK
    - especially for: reflashing the devkit. This hasn't been tested yet, and I don't plan to do that for a while...
    So I wouldn't try that for now if I were you...


    INSTALLATION OF YOUR SCSI ADAPTER
    =================================
    - if your SCSI host adapter card was recognized & it was installed correctly, skip this chapter and go to "installation of the wnaspi32.dll"
    - if you have a scsi adapter other than the adaptec 2940, google & try to find a compatible driver for Windows 7, install it, and go to "installation of the wnaspi32.dll"
    List of Adaptec cards compatible with Windows 7:
    http://ask.adaptec.com/scripts/adap...XJjaF90ZXh0PVdpbmRvd3MgNw**&p_li=&p_topview=1
    (Note that the 2940 family is marked as no driver included/planned, but you can use a compatible driver without problems: cfr next lines)
    - if you have an adaptec 2940 scsi adapter, download this compatible driver: "Adaptec AIC-7870 PCI SCSI Controller (emulated)"
    You can download it at the end of this page, look for the post of PhilWin7:
    http://www.winvistatips.com/adaptec-scsi-adapter-2940-lack-64-bit-drivers-t800611.html
    - go to the device manager
    - locate your unrecocgnized 2940 scsi adapter, right-click, select "properties"
    - click on the "update driver" button
    - select "browse my computer for driver software"
    - select "Let me pick from a list of device drivers on my computer"
    - from the list of common hardware types, select "storage controllers" and click "next"
    - click on the button "have disk"
    - browse to the path where you unzipped the driver compatible with the 2940 card, and install it
    - Windows 7 will install the driver, and should recognize the scsi card, and the Katana devkit GD-M & DA.
    If the installation is successful, you will see this:
    [GALLERY=media, 2238]Win7_DevMan00 by T_chan posted Aug 6, 2017 at 5:24 PM[/GALLERY]
    - When this is done, you will see the two devkit devices in the device manager:
    [GALLERY=media, 2239]Win7_DevMan01 by T_chan posted Aug 6, 2017 at 5:25 PM[/GALLERY]
    - If you don't see them, a reboot might help.


    INSTALLATION OF THE WNASPI32.DLL
    ================================
    - Download this replacement of wnaspi32.dll: MekugiAspi
    - You have two options: install it for your whole system, or just for the Katana SDK applications that communicate with the devkit.
    As the current version of MekugiAspi is still in early development phase, I would recommend to install it only for the Katana SDK apps.
    1) To install it just for the Katana SDK apps:
    - unzip MekugiAspi and copy the dll to the different subfolders of the SDK applications:
    eg. \Utl\Dev\Codescape
    \Utl\Dev\DACheck
    \Utl\Dev\GDWorkshop
    \Utl\Dev\DBFlash (-> you better not execute the reflash of the devkit with this version of MekugiAspi... this has not been tested yet)
    or:
    2) to install it for your whole system:
    - Windows 7 64 bits version: install the dll to C:\Windows\SysWOW64\
    - Windows 7 32 bits version: install the dll to C:\Windows\System32\


    RUNNING YOUR KATANA SDK APPLICATIONS:
    =====================================
    - for your shortcuts:
    - right-click on the shortcut, choose the "Advanced" button
    - select "Run as administrator" and click twice on "OK". If the system asks for Administrator privileges to change this setting, click on OK/Continue
    - when you execute the application directly by clicking on the .exe:
    - right-click the application, and choose "run as administrator" every time you want to launch the app, or:
    - right-click the application, choose "properties", go to the "compatibility" tab, and select "Run this program as an administrator"
    - When launching an application, the system will ask you if you want to allow the following application to make changes to your computer, just click yes.
    (it appears because we checked "run as administrator")
    - to check if everything went well, I would run DACheck & test the DA & the GD-M... if you get error messages or don't get two green buttons at the end, something's wrong...
    This was the result on my pc:
    [GALLERY=media, 2240]Win7_DaCheck by T_chan posted Aug 6, 2017 at 5:26 PM[/GALLERY]

    You're now ready to execute the Katana SDK applications again !

    Do not hesitate to leave a message if you're experiencing problems / have questions / are using MekugiAspi / ...
     
    Last edited: Aug 6, 2017
  2. pitsunami

    pitsunami 3DO maniac

    Joined:
    Nov 4, 2005
    Messages:
    649
    Likes Received:
    20
    Very nice tutorial... thanks a lot! :thumbsup:

    Btw do windows 7 show both partitions of the katana hard drive?
     
  3. T_chan

    T_chan Gutsy Member

    Joined:
    Apr 13, 2008
    Messages:
    448
    Likes Received:
    51
    No idea, I didn't test that...
    I reformatted the hdd of my devkit to 1 big FAT32 partition a long time ago, so I wouldn't know...
     
  4. skateforjondoe

    skateforjondoe Gutsy Member

    Joined:
    Aug 21, 2007
    Messages:
    451
    Likes Received:
    1
    Thank you T_chan.
     
  5. Evangelion

    Evangelion Spirited Member

    Joined:
    Jul 20, 2008
    Messages:
    108
    Likes Received:
    2
    Thanks for that, T_chan, it will be useful :)
     
  6. karsten

    karsten Member of The Cult Of Kefka

    Joined:
    Mar 14, 2004
    Messages:
    4,006
    Likes Received:
    124
    stickified. thanks for the effort.
     
  7. skateforjondoe

    skateforjondoe Gutsy Member

    Joined:
    Aug 21, 2007
    Messages:
    451
    Likes Received:
    1
  8. user

    user Newly Registered

    Joined:
    Dec 30, 2010
    Messages:
    1
    Likes Received:
    0
    Thanks, very useful.
     
    Last edited: Dec 31, 2010
  9. T_chan

    T_chan Gutsy Member

    Joined:
    Apr 13, 2008
    Messages:
    448
    Likes Received:
    51
    Update : I've released a new version of Mekugi Aspi, my replacement dll for wnaspi32.dll.

    Changes:
    - Enhanced compatibility:
    * devices with multiple LUNs are now recognized correctly
    * programs that called the wnaspi32.dll by using the function ordinals instead of the function names should be OK now
    * you no longer need a driveletter on the same port to have your devices recognized
    * HDD's are not filtered out anymore (I did that as precaution for the 1st release)
    * Added function GetASPI32DLLVersion
    Still not a 100% compatibility, but a big step in the good direction...

    What does that mean for the DC Dev hardware fans ?
    That with this new version, you can use the HKT-03 soundbox under Windows 7 :D
     
  10. dyer60

    dyer60 Site Supporter 2013,2014,2015,2016

    Joined:
    Jan 13, 2013
    Messages:
    423
    Likes Received:
    113
    Top work.

    Thanks a million really useful.
     
  11. -=FamilyGuy=-

    -=FamilyGuy=- Site Supporter 2049

    Joined:
    Mar 3, 2007
    Messages:
    2,910
    Likes Received:
    728
    T_chan, you're doing amazing work here!

    Cheers!
     
    Last edited: Feb 9, 2013
  12. Shane McRetro

    Shane McRetro Blast Processed Since 199X

    Joined:
    Mar 11, 2012
    Messages:
    2,074
    Likes Received:
    189
    Thanks T_chan! Echoing the above, thanks for keeping the bed warm on Dreamcast development.
    I'll need to pickup a few in the next few months and it is great to see it is being actively fixed up and worked on. :congratulatory:
     
  13. atreyu187

    atreyu187 Intrepid Member

    Joined:
    May 13, 2012
    Messages:
    625
    Likes Received:
    16
    Thanks so much for not only this but simply adding ASPI drivers to Win7. I got the latest version and it works so well I have removed my WinXP VM for all my Dreamcast needs. I can't being to tell you how helpful all this and you have been!!
     
  14. takeshi385

    takeshi385 Mojarra Frita Bandit

    Joined:
    Mar 29, 2011
    Messages:
    1,845
    Likes Received:
    150
    THanks for this.
     
  15. T_chan

    T_chan Gutsy Member

    Joined:
    Apr 13, 2008
    Messages:
    448
    Likes Received:
    51
    Glad to help.

    If you'd told me you were using an XP VM just because of incomplete wnaspi support on Win7, I wouldn't have waited 3 years before updating my dll :smile-new:
     
    Last edited: Mar 14, 2013
  16. atreyu187

    atreyu187 Intrepid Member

    Joined:
    May 13, 2012
    Messages:
    625
    Likes Received:
    16

    HAHAHA I am just happy someone deiced to add it back in, it wasn't to bad hacking games with XP VM just time consuming as it took much longer to build, hack, and transfer data to and from the HDD's. I am honestly surprised this hasn't blown up and a lot more folks interested. ;)
     
  17. -=FamilyGuy=-

    -=FamilyGuy=- Site Supporter 2049

    Joined:
    Mar 3, 2007
    Messages:
    2,910
    Likes Received:
    728
    Doesn't winaspi32.dll work on windows 7? I always assumed it did... in fact I think I've burned cd-r using old cdrecord, cygwin1.dll and winaspi32.dll... or maybe was it using a newer version of cdrecord?

    Of course, meguki is mandatory to use a devkit.
     
    Last edited: Mar 15, 2013
  18. atreyu187

    atreyu187 Intrepid Member

    Joined:
    May 13, 2012
    Messages:
    625
    Likes Received:
    16
    Frogaspi works but not as good as this driver does so I stuck with a xp vm till I got this driver.
     
  19. CHAOTIX

    CHAOTIX Active Member

    Joined:
    Jul 6, 2013
    Messages:
    48
    Likes Received:
    0
    Thanks so much for this - got my 5.24 all back up and running with this awesome guide.

    Now if I could just get code warrior to work properly!
     
  20. Woofmute

    Woofmute Site Supporter 2013-15, 17

    Joined:
    Jan 18, 2010
    Messages:
    183
    Likes Received:
    32
    Yes, I cannot recommend this enough!

    Also, this aspi replacement did work for me each time I've reflashed under Windows 7, so you should be okay, provided the unit is connected and terminated properly.

    My only issue though is that my adaptec 2940 card wouldn't work at first until I changed some settings. Now whenever I boot with the dev kit connected, Windows 7 will hang at the windows logo screen for about 1-2 minutes, almost as if it is waiting for something on the scsi chain and then times out. Is this normal behaviour? My unit is properly terminated with active terminators, and is connected to SCSI-A with ID's 3 and 4 set.
     

Share This Page