Nologic

I'll look into this...I got dual monitors so I should be able to off set the Open dialog box to the other monitor to check and make sure its closing the way its should. Any ways you've done a great job of getting the issue narrowed down...to kenclops & my self will see if we can get it resolved for you.

Heh well I didn't until you mentioned it. I hooked up another gamepad and bam So I'm looking into it now.

Actually the other version doesn't require daemon tools, but it does require a virtual drive of some sort...it just assumes daemon tools is all. Matter fact I posted that I to was running into issues with daemon...I tried it with Alcohol 52% as the virtual drive and all is peachy in that respect. Now to the biz here. Are you closing the loader with a key-combo by using an advanced config...much like whats used in the my version...or are you exiting the emu by pressing ESC? If key-combo...this build doesn't currently have a child program to pick up the slack to make sure every thing turns out roses...if your exiting the emu...you got me...at a glance it should ideally be working correctly...tho something some how got lost in the details. Hehe some thing that happens to me all the time...no surprise there eh?

Thanks I'll take a look. I have one way more or less figured out...but its rather ugly...trying to think of a better way of going about things to where its less of a headache to get things up and running.

Okay just tested using Alcohol 52% free edition and I'm no longer having that issue any more...and the disc images seem to be un/loading faster. _settings.in looks like [Virtual_CD] Command_Mount=C:\Program Files\Alcohol Soft\Alcohol 52\AxCmd.exe 1: /M:"[RomPath]\[RomFile]" Command_UnMount=C:\Program Files\Alcohol Soft\Alcohol 52\AxCmd.exe 1: /U [Xpadder] Pathing=C:\Program Files\Xpadder\Xpadder.exe Course in defense of Daemon Tools I am using 4.00 not 4.08 the most current build...so the issue I'm experiencing maybe resolved in newer builds.

Well I've tried to properly exit nullDC...but its still not releasing its calls to Daemon Tools correctly it seems. Secure mode shouldn't make a difference I would think...tho I'm no expert when it comes to Daemon Tools. Maybe I'll try some other virtual drives and see if there is the same issue...if so it'll be some thing the nullDC team will have to solve. Things can still be made to work...as seen with the other loader...we can access the images directly from the drive...it just seems a bit more unsightly is all...hence why I tried to avoid it in the first place. Anyways we'll see how things pan out...but right now things aren't looking to bright for virtual drive access.

I think the system tray icon is an older bug with windows if I recall correctly. I am however bumping into issues where Daemon Tools is unable to unmount the disc image of the game exited...this might be causing problems for you and others as well. Maybe nullDC isn't correctly releasing the disc image...which maybe true as I'm forcing a close of the process. Hehe I may have to clean that up for it to work more correctly.

Yeah the script is written to cause Xpadder to close...but its also suppose to reopen it again when you launch into another game...so..hmm...I'll look into things

Not likely. heh but worth a try I guess.

So its still in the middle of the screen?

Hehe okay...then after you got that all sorted out...we'll look at the next issue.

LOL doh! I'm screwing up all over the place today. http://fileforum.betanews.com/ it was news...not files...blah

Your welcome

Doh! I did it again....blah should have been Opt("MouseCoordMode", 1) As 0 sets the mouse cursor to be moved based on the active window...rather than the whole of the desktop. Hehe my f!up

hmm this should have done it ; Move Mouse to Lower Right Corner MouseMove ( @DesktopWidth , @DesktopHeight , 1 ) Keep in mind "@DesktopWidth" wasn't some thing you where to change...that actually a AutoIt macro that grabs the width of the desktop...same for the height one...since the mousemove command works from the upper left corner which equals 0,0 so putting: MouseMove ( 0 , 0 , 1 ) Would move the mouse to the upper left corner of any desktop and: MouseMove ( @DesktopWidth , @DesktopHeight , 1 ) should put it in the lower right corner and: MouseMove ( @DesktopWidth / 2 , @DesktopHeight / 2 , 1 ) should put it in the middle of any screen as we are dividing the height and width of the desktop...no matter what it is. MouseMove ( 10 , 20 , 1 ) Would move the mouse cursor 10 pixels to the right of upper left and 20 pixels down from upper left MouseMove ( @DesktopWidth - 10 , @DesktopHeight - 20 , 1 ) Would place the cursor 10 pixels to the left of lower right and 20 pixels above lower right. Heh well its good your starting to gain a grasp of it.

Well GameEx monitor's the process that it spawns...it doesn't monitor process that are started from the parent. So as is the script out side of GameEx launch's nullDC, manipulates nullDC into loading a game...then exits, leaving nullDC all by its self. So as we know from prior history as soon as the process ends that was spawned from GameEx its self, it reasserts its self...this is where the problem lays. So to solve this we need to keep the load active...as long as nullDC is. Thus we add the following code: ; Wait for Emu to Exit ProcessWaitClose ( "nullDC_100b1.exe" ) ; Close loader Exit ; EOF

Sure why not?

Meaning that you have all the required drivers and such installed, and that the system can access the internet encase you run into problems.

Okay if you go to your AutoIt Programs folder with in the Start Menu you'll see a shortcut called "AutoIt Window Info" this little app will grab you all the info you typically need to know about a given window. 1.) "ndc_main_window" is the class name for the main window form...as rather than the command console. There are different options for how you would like to identify a given window...I choose a way thats more universal...so should nullDC become multilingual it won't effect the script if its on a English system or a turkish system. 2.) this gain is much like the prior...its the actual ID given for the control as its spawned...don't matter what lang the system is...it'll always react correctly to that control. 3.) thats to redisplay the window...its suppose to be launched hidden...so that all you acutally see is the menu dialog as it opens...that is till the open file dialog opens...as I didn't try and hid it...basically its a hold over from my original script. I was trying to keep things as clean as possible...thats why I wrote the script the way I did...other wise I could have written it like this and put in some testing to see if the file is cdi gdi or what ever and then behave accordingly. 4.) holds down the ALT key then press f for File then n for Normal then releases the ALT key...its the best way to handle accelerator shortcuts in and on menu's. Hehe read the above post where I describe a screw up on my end. Hehe cool good to see some of my spam leading others into uncharted waters.

Well make sure you got the 98 box up and net worthy before you touch the other one.

Damit....I did it again. I update every thing above...problem was I used the wrong command line var...some thing I've goofed on before. I used "$CmdLine[0]" which is the count of how many commands are being sent to the executable...."$CmdLine[1]" is the first command...and "$CmdLine[2]" would be second...so on and so forth.

Oh the Boot to CD option is some thing that typically needs to be enabled in the computers BIOS...along with placing the CD drive as the first drive to try and boot from....well at lest prior to any hard drive.

Newer systems can boot from CD natively...so you'll typically see some thing during start up like: To boot from CD press (Space)... All you do then is press the spacebar WinXp install disc will bootup in a DOS shell like environment that you'll have to push buttons to navigate through...and at some point it'll ask you how or if you want to partition and\or format a drive...and which drive to install to. So..yes and no.

No idea off hand but I normally go hunting around Betafiles.com's FileForum for app's to play with...so I'd suggest heading over there and taking a look and see if anything fits the bill.

Try the below code ; Open Dialog WinWaitActive ( "Open" ) ControlSetText ( "Open" , "" , 1148 , $CmdLine[1] ) ControlClick ( "Open" , "" , 1 )