Nologic

Win9x is just a shell over DOS, so yes. Now any thing prior to Win9x you would be required to install DOS before windows.

Actually the help file is a blessing in AutoIts case...very very informative with lots of sample code that I steal from often. Generally you want to stay as far away from "Send" keys as possible...if some thing steals focus your screwed. Any ways look over the code...read up on it...and then improve upon it.

Basically once the floppy is done all you should need to do is boot from it, and enable CD support and then just pick up where you left off...and thats copying the files from the CD to the hard drive.

correct its not finding the CD drive...and you booted from the Win88 floppy? if not you need to.. boot98se.exe...is an executable that when launched will prompt you to have a floppy in your A:\ drive at which point it will install its self onto the floppy...once done the floppy will now be able to boot your system...and provide you with CD support should you press the correct option to enable it. Hehe we are going from memory here...and its been a long long time.

Okay set the filter to *.cdi Command Line to: loader.exe "[ROMPATH]\[ROMFILE]" ; AutoIt Options Opt("WinTitleMatchMode", 4) Opt("MouseCoordMode", 0) ; Check For Valid Commandline If NOT $CmdLine[0] = 1 Then Exit ; Launch Emulator Run ( @ScriptDir & '\nullDC_100b1.exe' , '' , @SW_HIDE ) ; Load Game WinWaitActive ( "classname=ndc_main_window" ) ControlSend ( "classname=ndc_main_window" , "" , "" , "{ALTDOWN}fn{ALTUP}" ) ; Open Dialog WinWaitActive ( "classname=#32770" ) ControlSetText ( "classname=#32770" , "" , 1148 , $CmdLine[1] ) ControlClick ( "classname=#32770" , "" , 1 ) ; Display Emu WinSetState ( "classname=ndc_main_window", "", @SW_SHOW ) WinActivate ( "classname=ndc_main_window" ) ; Move Mouse to Lower Right Corner MouseMove ( @DesktopWidth , @DesktopHeight , 1 )

Okay there is some work to be done here. When you see an AutoIt command that has [...] what ever is between the brackets is optional...and the brackets are not suppose to be there. Also one script per disc image is a lot of work thats not needed. Any ways give me a second to look things over and we'll see what we end up with.

http://www.bootdisk.com/ grab the Win98 SE build Okay now since you got the partition recreated, A:\>format C: /q Reboot with CD support A:\>md C:\Windows A:\>md C:\Windows\cabs A:\>copy D:\Win98\*.* C:\Windows\cabs\ A:\>cd C:\Windows\cabs\ C:\Windows\cabs\>setup.exe If any files get requested during setup point it to C:\windows\cabs\ first off...speeds up installation over all and saves a bunch of headaches later on. Oh and go here to learn how to really f!up Win98

Well I do hope the suggestions help...tho other than Xpadder its all guess work.

Extract the attached folder contents to your desktop Copy Delta_Loader.exe & Kill_Emu.exe to your Delta install folder Copy "[Console] Sony Playstation (ePSXe).ini" from "*\Support\Import\" to "*\GameEx\CONFIG\EMULATORS\IMPORT-EXPORT\" Copy "[Mapping Off] Exit (Process Close).inii" from "*\Support\Import\" to "*\GameEx\CONFIG\EMULATORS\" Fire up "Advanced Configuration" Press "Next Page" till you come to a free Emu button then click that button From the drop down menu for "Import Emulator:" select "[Console] Sony Playstation (ePSXe)" Press the "Import" button Press "OK" on the overwrite dialog box Correct directory pathing if required (more than likely) Press "Save" Press "Exit" Notes: Make sure your Rom path is pointing to where your *.dt2 files are for the PSX...by default this is "C:\Program Files\Delta\Config\Psx Games" I personally have ran into problems using the Moby CDR plugin, and have found using the default ISO plugin to work fine thus far.

oh shit...yeah sorry about that vista isn't supported by the AutoIt Build I'm using...give me a sec I'll go see if there is a newer build that does support Vista. Not finding any thing as of yet....try right clicking on the autoit executables and selecting "Run as.." or "Run as adminstrator" and see if that solves the problem. Also Xpadder's executable will need the same as above...tho you haven't reached that issue as of yet. I'll keep trying to hunt down info to get every thing working...sorry for the let down thus far.

try using the fdisk command from dos to create a new partition. the nicest way to go about trying to get things to work is to have a recovery CD that you can boot to. BartPE CD\DVD Ultimate Boot CD UBCD4Win 911 Rescue CD

It sounds like you destroyed your boot sector on C:\. Every thing else is just a cascade of that...nothing is destroyed more than likely other than data.

Well just dug up the command line options for Pinnacle...so far I think its the only gamepad mapper that has decent support for CLI. If there are any others let me know.

Yeah I'll see if there is some way I can come up with using nullDC's built in disc abilities. I'll take a look at Pinnacle...I've never toyed with it...but maybe now is a good time to. We'll see what happens.

Well there was a second update....that you didn't grab I managed not to pass the right info to the loader...as noted above. Give me some details about command line usage for epsxecutor...including what your links look like. Also export your epsxecutor settings to a reg file so I can browse that as well. Hehe the more info I have the faster and more clean I can do things with out stumbling around in the dark hoping to get things right.

Extract the attached folder contents to where nullDC is installed Copy "[Console] Sega Dreamcast (nullDC).ini" from "*\Support\Import\" to "*\GameEx\CONFIG\EMULATORS\IMPORT-EXPORT\" Fire up "Advanced Configuration" Press "Next Page" till you come to a free Emu button then click that button From the drop down menu for "Import Emulator:" select "[Console] Sega Dreamcast (nullDC)" Press the "Import" button Press "OK" on the overwrite dialog box Correct directory pathing if required (more than likely) Press "Save" Press "Exit" Edit the _settings.ini file to where it match's the syntax and pathing required to mount and unmount a CD image with your given virtual drive (daemon tools is assumed) While the loader is setup for daemon tools...its advised to use a different virtual drive application Alcohol 52% works fine. Create a Xpadder profile for nullDC called "nullDC.xpadderprofile" save it to your nullDC folder Make sure that for your GDRom Plugin you have the following selected: zNullGD, SCSI Passthru GDROM Plugin By _ZeZu_ [Apr 1 2007] v1.0.0 (zNullGD_Win32.dll) Note this setup doesn't currently support GDI dumps.

Actually my primary system emulates the PS2 fine in general...mostly growing pains of the Emu. Believe it or not the DC is running rather fast on some fairly old systems (old in computer terms 3-5 years+ old)

Unless you plan to run the PS2 emu on the cab...the Athlon XP will more than good enough. watts are the same between the two cpu's if I recall correctly. Onboard video quality varies...I have yet to really seriously toy with my HTPC so I can't say whether its good or bad and its got the GeForce 6150 onboard...just know it'll never run the PS2 emu ever.

I've spent a little time over @ ngemu's forum as of late...past that I'm typically here seeing what new idea's others have come up with.

There is no command line options as of yet for nullDC but its suppose to be in the works...likely the next release coming up here shortly. I could write a script that does all the button pushing for you to load a disc image...but mine are mildly slow...HK would be the man to talk to about getting a loader\wrapper written up thats lighting fast. However nothing beats a native CLI

I'll lend some advice here in a bit...got some thing else I'm trying to get wrapped up with far as ePSXe first.

Removed see further down the page.

Well JoyToKey is a little better than ControlMK which is barely better than native support thats in GameEx...however I don't think ControlMK is able to load a profile via the CLI so its generally in the same boat as Xpadder...only thing that Xpadder has over the others is its huge feature set. A quick break down GameEx + Close Process + Close multiple process's + Per Emu bind mapping - Per game bind mapping - Support for dual analog joysticks - Documentation - Multiple gamepad mapping - Macros + Mouse - Rumble\force feedback - Triggers - Toggle fuction - Turbo fire - Joystick deadzone adjustment - Gui ControlMK - Close Process - Close multiple process's - Per Emu bind mapping - Per game bind mapping + Support for dual analog joysticks - Documentation + Multiple gamepad mapping - Macros - Mouse - Rumble\force feedback - Triggers - Toggle fuction + Turbo fire + Joystick deadzone adjustment + Gui JoyToKey - Close Process - Close multiple process's + Per Emu bind mapping + Per game bind mapping (real bitch to do) - Support for dual analog joysticks - Documentation + Multiple gamepad mapping - Macros + Mouse - Rumble\force feedback - Triggers - Toggle fuction + Turbo fire + Joystick deadzone adjustment + Gui Xpadder - Close Process - Close multiple process's + Per Emu bind mapping + Per game bind mapping + Support for dual analog joysticks - Documentation + Multiple gamepad mapping + Macros + Mouse + Rumble\force feedback + Triggers + Toggle fuction + Turbo fire + Joystick deadzone adjustment + Gui

*keeps pillow and blanket close* hehe Okay continuing with feedback. GameEx currently doesn't support two or more different gamepad mapping's used at one time...course it doesn't support two or more controllers so not a big whoop. GameEx currently doesn't support per game, gamepad mappings.

bkenobi your correct in your assumption...anyways I'll get something put together later today for you that should do the trick.