benners

As far as I Know there are no guides, there are examples in the help file and some examples on the Indigo Rose website, but I wouldn't post there if you haven't bought the software but are using it via dodgy methods as they ask for your key sometimes to verify. I have only used version 4, trialed version 5 and they changed the whole layout, so need a few spare months of trial and error to learn, thats how I learnt before.Just set aside the rest of your life to learn and you should be ok Just noticed the links at the top of the page advertising various other menu creators, if you don't want anything to complex you could try a more simpler program, to get the gist, then advance to APMS (Autoplay Media)

The project files, at least for version 4, end with am4, and editing cannot be done without these am4 files.The extensions of the files used in the project are renamed by the Autoplay program, this is I assume , just to discourage the end user from editing, or tampering with them, if you know the original extension you should be able to rename them or open them with the appropriate program. IMHO is just short for In My Humble Opinion.

My guess is its been built from scratch to run their programs, the exe, and there should be an apm file, are encrypted on compile, the background is a bitmap or jpg renamed by the program, probably menu1.bah or the dah files. Buttons can be images that have a rollover effect, i.e change on mouseover, 2 or 3 different pictures are used to produce the effect, or they could be just text objects, hard to tell from the picture or without seeing it working.The text on the right can be set to change as you move over the different buttons on the left and the executables that run are at their most basic level, browsed to, then the path is setup in the apm file

****, I must be a retard, it has taken me since I signed up to this forum to create, design autoplay menus and perfect my tweaked disc, (yesterday ). Like a few people have mentioned, I think it is interesting too, I have learned a lot of stuff, had a few all nighters testing and improving and as I was the first port of call to fix, repair and do a wipe and load on other peoples puters it has saved me time, (its also kept me awake at work), when you are the most experienced person in your circle of friends etc, you feel like your the s***, but after reading post on this forum you realise your just s*** and wonder why Bill Gates doesn't employ some of the participants of this forum. Before doing this disc I spent ages creating Autoplay menus that I manually ran, and even though the settings were imported from reg files and exes replaced with a click of a button, it still meant I had to sit there doing it and there was always a tweak that I picked up from the net, applied then forgot about, then spent ages trying to remember where I saw it, now everything (I Think) is commented for easy searching and have discovered Wraith's ace Xplode that has replaced a few batch files that copy the current files and settings from C: drive to their correct folders on my XP DVD. Bit of a long winded way of saying "Yes", but yes it is worth it.

Well it looks like a few people have had that sinking feeling , but lets face it how much of the "insert number here"gigs were there 'cos you didn't want to delete it 'cos you have downloaded and may require the use of 20 different text editors or Antivirus programs in some parallel universe, I for one

That menu was created with Autoplay Media Studio, if you have $400 you can get it here . There are other products but none are as advanced IMHO, just Google autoplay menu makers.

ffdshow, I use setup.exe /S

As for coverXP, all I use is the directory created after install, drop it in $Progs and import the reg key at [HKEY_CURRENT_USER\Software\coverXP]

If you use AutoPartition=0 this will prompt you for a partition and drive to use, I use this as I too have multiple drives, and the odd minute it takes to choose is better than the cold sick feeling you get when you have just formatted 20 gigs of useful stuff. If you have two drives and you are sure that it will pick the correct one during the text setup portion you can set it to =1, I think if you formatted the second drive as an extended partition, setup would choose the primary active partition of the other drive, just test run setup to the format stage and see which drive is chosen as the default, or set AutoPartition=0 (Which is my recommendation) and choose.

Yep that is similar to the method I employ, but mukeshnuna seems adamant that he doesn't want to copy anyfiles to the HD.

#Sourcepath# is a variable that is specific to Xplode, and as such can only be used in your Xplode xml file or with switches related to Xplode i.e /xml:#Sourcedrive#\drivers\another.xml and I suggested using #SOURCEDRIVE# instead of #SOURCEPATH# .If you want to run it from CD you should add this line to your xplode.cmd file for %%i in (D: E: F: G: H: I: J: K: L: M: N: O: P: Q: R: S: T: U: V: W: X: Y: Z:) do if exist %%i\win51ip.SP1 set CDROM=%%i this will scan all the drives and look for the win51ip.SP1 file, or any file you specify and if it finds it, it will set the %CDROM% variable to the drive letter, you then use this in your xplode.cmd to point to your Xplode.exe file

I don't think you need the extra quotes, try it using this code "..\Xplode\XPlode.exe /log:#systemdrive#\xplode.log"

Try setting overlay='#FF00FF'

I may be wrong but, I think that that #SOURCEDRIVE# and #SOURCEPATH# are variables specific to the xplode program, the values which are read from the registry. The #SOURCEPATH# variable would point to the location of the I386 folder.On a CD or DVD (drive letter of E:) with multiple I386 folders this could E:\ROOT\PRO4, and #SOURCEDRIVE# would be E:\, on a disc with only 1 I386 folder on the root of the cd they would be the same, I just think it is better to use #SOURCEDRIVE# to be certain of getting the correct value.

In your cmdlines and xml code, use # to surround the variables instead of %, and if you use the /s switch with regedit there will be no confirmation dialog asking you to apply the registry tweaks arguments='/s #SOURCEDRIVE#\PostInstall\registry.reg'/> I have changed #SOURCEPATH# to #SOURCEDRIVE# as I think #SOURCEPATH# equates to the I386 folder on your cd.

if this is the case then your path to xplode.exe is incorrect in your xplode.cmd file, this is pointing to %systemdrive%\Xplode\Xplode.exe as %Systemdrive% is a variable for the drive where windows is installed, usually C:\, it is not looking on the cd for the executable file. If your $OEM$ directory is also on the root of your cd you could try ..\xplodeXPlode.exe /log:#systemdrive#\xplode.login your xplode.cmd file, as currently the log file will try to be created on your cd.

@prathapml thats what I have been up to last night, and although I miss the mask and guitransparent functions, as you say this does work without errors or hangs, and your right I was using v1.1.2, there are some changes needed to my DVD layout but it does look better than the RunOnce method.As for bugging Wraith, I don't think that was the case, this is the first time I have asked for help from anyone (I think ) since joining, and, never pressured anybody for a solution, I did search so I did save Alanoll from having to refer me to the search engine , I understand that no one is under any obligation to help and sometimes you can get p***ed off when people ask questions that are already answered but, I suppose if you have skills, and share your work as happens frequently here, you gotta expect people are gonna post their problems. /rant>. The reply to my post in current development did seem irate, and I didn't reply because it would have probably kicked off and clogged a genuine thread up with bitchy remarks.So thanks to all for your suggestions, I'm off, back to typing.

Well I don't know if it is a bug or not, but, I posted a query here and have the same problem as MCT here, when I run taskkill it says Error:Critical Error. I have tried the copying of files and shortcuts at T-13, T-12 and from Gui RunOnce, no joy, the files do seem to be copied but the install hangs after.If you could help Wraith that would be great

The only way to know for sure is to try, Run the drivers setup with the -R switch, i.e setup.exe -R, choosing the components you want installed, there should be a file created in your windows directory called setup.iss, copy this to where your EXE is. Add the setup routine to your install.cmd file something like this, name of EXE -s -f1\location of setup directory\setup.iss and maybe use -f2\"%systemdrive%\setup.log if you are running from CD-Rom, this will tell the setup program where to create the setup.log file. Sometimes you can get away without using the f1\ switch and use setup.exe /s, the program will by default look for the .iss file in its own dir, my Intel chipset drivers and Nvidia gfx drivers for the laptop do it.

try changing UnattendedSwitch="Yes" to UnattendSwitch ="Yes"

Here's mine

@Alanoll I tried it with a trailing \ when I implemented the code you suggested previously, it is in the code section from my xplode.log in my 2nd post, Tag: 'copy' { source = 'D:\XP DVD\Applications\apms\settings.ini' target = 'C:\Program Files\AutoPlay Media Studio 4.0\Data\' it looks like Xplode removes the \ from the line when it executes, Copying file: 'D:\XP DVD\Applications\apms\settings.ini' -> 'C:\Program Files\AutoPlay Media Studio 4.0\Data' Error: maybe Wraith subscribes to Microsofts credo of

@killerbee I placed a directory called files in the $oem$\$1 folder and used this <item display='Autoplay Media Studio'> <execute display='Installing Autoplay Media Studio ' program='#sourcedrive#\Applications\apms\setup.exe'/> <copy source='#systemdrive#\files\Preferences.xml' target='#programfiles#\AutoPlay Media Studio 4.0\Data\Preferences.xml'/> <copy source='#systemdrive#\files\settings.ini' target='#programfiles#\AutoPlay Media Studio 4.0\Data\settings.ini'/> </item> but it froze again and does not display the description of the current operation.I also tried it using the mask option <copy source='#systemdrive#\files' target='#programfiles#\AutoPlay Media Studio 4.0\Data' mask='*.ini'/> but that also failed, I will wait until Wraith graces us with Xplode v2 and see if I am able to install at T-12, if not I will install the apps from there and either create sfx archives in Winrar to do the copying and deleting or run after first logon, just not as neat though . If I get the time I will try installing from svcpack.inf, just would like to know if other people have had any luck installing\copying and deleting at this stage in the setup.

Nope still no joy } Items Block { Item Block: 'Autoplay Media Studio' { Tag: 'copy' { source = 'D:\XP DVD\Applications\apms\Preferences.xml' target = 'C:\Program Files\AutoPlay Media Studio 4.0\Data' } Tag: 'copy' { source = 'D:\XP DVD\Applications\apms\settings.ini' target = 'C:\Program Files\AutoPlay Media Studio 4.0\Data\' } } } } Starting dialog { } Execution thread { Running item: 'Autoplay Media Studio' { Running command: 'copy' { Command: copy, (3,0) Copying file: 'D:\XP DVD\Applications\apms\Preferences.xml' -> 'C:\Program Files\AutoPlay Media Studio 4.0\Data' Error: } Running command: 'copy' { Command: copy, (3,0) Copying file: 'D:\XP DVD\Applications\apms\settings.ini' -> 'C:\Program Files\AutoPlay Media Studio 4.0\Data' Error: } } } -=-=-=-=-=-=-> XPlode end at: 04/07/03 19:45:25 I also added a trailing slash and, tried absolute paths but these did not work in windows. Thanks for your reply, looks like Babylon 5 season 2 is going to have to wait

I am running xplode at the T-12 mins stage from cmdlines.The hotfixes and programs install ok but when it comes to deleting or copying files Xplode hangs, the commands in the xml file work in the Windows enviroment but not at the gui stage of install. This works, <item display='Adding Start Menu Shortcuts'> <copy source='#SOURCEDRIVE#\Applications\$allusers\pro3' target ='#AllUsersProfile#' mask='*.*'/> These dont, <delete source='#AllUsersProfile#\Start Menu\Programs\Alcohol 120%'/> <copy source='#SOURCEDRIVE#\Applications\apms\Preferences.xml' target='#ProgramFiles#\AutoPlay Media Studio 4.0\Data\Preferences.xml'/> <copy source='#SOURCEDRIVE#\Applications\apms\settings.ini' target='#ProgramFiles#\AutoPlay Media Studio 4.0\Data\settings.ini'/> the xplode.log does not show any errors or files being deleted Starting dialog { } Execution thread { Running item: 'Alcohol120%' { Running command: 'delete' { Command: delete, (3,2) } } } Is this a bug or operator error?