Jump to content

Nanaki

Member
  • Posts

    507
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Posts posted by Nanaki

  1. Crap, I forgot about this.

    Try this one, if you still need it.

    I have no flying idea what the problem is, but this version restarts itself every half hour.

    The only thing close to a debug mode is the "/k"-parameter. It makes a C:\cdswitch.txt logfile, but the only thing you (or I, if it keeps happening) will learn from it is how long it stays alive.

  2. To be honest, I never tested this situation (or even thought about it).

    I dusted off some old digital folder and took the (non-WPI) 0.8.4-version of CDswitch (there are probably newer and better versions I made, but I don't feel like puzzling them together). I'm going to give you the only solution I can think of: a fresh compilation.

    Since I see you're using x64, here's a x64-version: click.

    And if it doesn't work (I have no idea, still using the same 4-year old pc, can't even test it), here's a normal version: click.

    Now, I had to change a couple of lines to make it build, and I can't even test the basic functionality (my disc drive doesn't work, maybe due to the excessive testing of this tool a couple of years back :)) so no money back.

    Next to that, does the "/s"-parameter even work? I never tested it during a windows-installation and certainly not on Vista (it refers to a windows-tada-sound if I remember correctly).

    cheers,

  3. Hello all,

    I was wondering if anyone is using the disc spanning tool "cdswitch" because i have a couple of questions on setup. I would just like to know the easiest way of integrating it into "wpi". I have been searching the forums and I keep coming up with using cdswitch in different customized ways but none that just explain how to simply integrate it with WPI. I have tried batch files, preinstalling, running commands from the wpi commandline, and more. all i want to

    do is my usual wpi install(around 5gig) but i want it spanned over CD-Roms(i have a bunch of laptops that dont have dvd-rom drives that i need to wipe). thats it, no fancy pics or font size or antyhing. as u can see i am frustrated so pardon the sarcasm. as always any/all help is greatly appreciated. THANKS

    I've kinda of forgotten the usage of my own program (loss of time and such) but I'll try and help you. Also note I've never used WPI.

    Here are some points:

    - If you use one "global" WPI (read: not one WPI per disc) it's probably better to copy WPI to the hard drive and then running it (via the $OEM$-folders or something, you probably know more about this than me).

    - If I derive from this post correctly, you can assign different "commands" to an installer in WPI. You can simply make "cdswitch" the first command to precede every installer:

    command 1: cdswitch OFFICE2003 %CDROM%
    command 2: %CDROM%\office\setup.exe

    Note 1: the %CDROM%-variable is a WPI-variable, see other topics for this.

    Note 2: cdswitch should normally detect if the correct disc is already inserted, and then close itself automatically, so you shouldn't worry about spawning an unnecessary cdswitch-window before every install.

    - So, in short, here's an example setup:

    Disc 1:

    • Label: "DISC_ONE"
    • Contains main Windows-stuff and WPI and maybe some applications.
    • CDswitch should be launched with command:
      cdswitch "DISC_ONE" %CDROM%


    • WPI-installer entry example:
      command 1: cdswitch "DISC_ONE" %CDROM%
      command 2: %CDROM%\installers\setup.exe


    Disc 2:

    • Label: "DISC_TWO"
    • Contains main Windows-stuff and WPI and maybe some applications.
    • CDswitch should be launched with command:
      cdswitch "DISC_TWO" %CDROM%


    • WPI-installer entry example:
      command 1: cdswitch "DISC_TWO" %CDROM%
      command 2: %CDROM%\installers\another_setup.exe


    I never tested the above, but in theory it should work. You should know more of WPI than I do to make something of the above.

  4. I'm not sure how to fix the bug (since I can't even reproduce it).

    I do know the bug that's causing the flickering in 0.8.5, but it would take more time to fix that one than to rewrite the whole thing (which I should one day do). :)

    Like all things... if only I had more time.

    CDSwitch 0.85b can be found here and it works a charm.

    And, hopefully, soon on the first page. :)

  5. Yep, a known issue. Windows is incorrectly painting CDswitch on screen, due to it being loaded all early and stuff. CDswitch 0.8.5b contains a fix for this (I really should consolidate the versions, maybe some time later), but I haven't incorporated this change into later versions yet, because it makes CDswitch "blink". I'll probably add a parameter "--repaint" or something like that soon.

  6. 1. Make sure cdswitch.exe and WPI.jpg are on the hard drive, not on a CD.

    If so, try placing the attachment (cdswitch.ini) in the same folder as cdswitch.exe and removing "/p:WPI.jpg" from your parameters.

    If that doesn't work, try resaving WPI.jpg as a bitmap (WPI.bmp) and see if that works.

    If all that doesn't work or you don't want to do those, just send me the picture you're trying to display.

    2. So after inserting a new disc, WPI asks what programs to install? It might be better to ask for help on the WPI-forum for this one, since I never used WPI before. Sorry. :/

    cdswitch.ini

  7. Alright, here's the deal: I don't really have time to look into this, with exams 'n everything. So I can only offer you a workaround that might not work (since I don't know the exact problem anyway). Until my precious time returns.

    Anyway, I think CDswitch is having some trouble running DOS-command scripts under certain situations, and those seem to exit too soon (well, windows is having trouble with it, but meh).

    I presume you run everything with GUIRunOnce, right? Well, at this time, run a super-duper-batchfile that takes care of the others;

    [GuiRunOnce]
    %systemdrive%\install\batch_file.cmd

    CMDOW @ /HID

    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.SP2 SET CDROM=%%i:

    start /wait %CDROM%\stuffthatshouldinstallfromdiscone.cmd

    start /wait cdswitch COLOSSUS2AP %CDROM% /p:%CDROM%\pic.jpg /ll:50 /lt:15

    start /wait %CDROM%\wpi.cmd

    That's how I installed back in the days I still made unattended installations, sort of.

  8. ...

    If I understand correctly, try this:

    cmdow @ /HID

    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.SP2 SET CDROM=%%i:

    start /wait cdswitch COLOSSUS2AP %CDROM% /r:%CDROM%\wpi.cmd /p:%CDROM%\pic.jpg /ll:50 /lt:15 /rw
    ECHO.
    EXIT

    Its good that it searches only optical drives. :)

    Now, if only someone could test it with BD and HDDVD. =)

  9. Alright, the stuff I'm about to say might not be fully correct, since I don't have the resources to test it and it's been a while since I've written this code.

    First, if you want to EJECT the drive containing the disc with certain file:

    cdswitch "" /f:"director\agent\windows\i386\FILES\dir5.20_agent_windows.exe" /l:"IBM Director 5.20"

    Notice how "X:" is omitted from the path, "/f" works like this.

    Second, you want to check the new disc for a file:

    sorry, not possible, this required a major overhaul of the code for it to work properly. I might try and put it in quite soon (just for you :P), but first I need my laptop back for that. I'll try and see later today.

    edit: try this one. I've found the disc I needed, so here's another new version.

    Use this code:

    cdswitch /f:"director\agent\windows\i386\FILES\dir5.20_agent_windows.exe" X: /l:"IBM Director 5.20"

  10. Is there anyway of using this if the CD happens to have no label??

    I've uploaded a version with a fix here. In my small tests, it worked with an empty label (still use double quotes "").

    OK Nanaki, I got it.

    As I don't know my driveletter, what I needed to do is :

    cdswitch DELL_RESSOURCES 1

    Ok, good to hear. :)

  11. suggestions:

    hint. im working in cmd...

    1. when cdswitch /v /c /f:<file> in cmd window (first time) there is no variable in, but when i reload cmd it shows

    is it fixable?

    2. when cdswitch /v /c /f:<file> second time and installation cd/dvd is in other drive, in cmd sill is old variable, must reload cmd

    is it fixable?

    3. when cdswitch /v /d in cmd variable still exist (even if i reload cmd)

    is it fixable?

    4. is there (or will be) option to check if variable exist and it differes from new one, in cdswitch, eg.

    i've CDDRIVE=l: but i put cd/dvd disk to other drive and i want to be sure is CDDRIVE variable is correct, if not rewrite it or submit errorlevel

    5. (question), there are errorlevels, but echo %errorlevel% in cmd is still 0 ;) is it fixable?

    btw. sorry for my bad english...

    1, 2, 3. cmd loads the variables at the startup. When you "load" cmd, it "loads" the variables. Pretty much nothing I can do about it.

    4. Nope, there isn't, sorry. :) Maybe later, or a separate app, heh. :P

    5. God, I once implemented it, but I have no idea what the state is on that. I should check that. :P

    I do it with a single line of code

    for %%i in (C 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.SP2 set CDROM=%%i

    You can replace the file details to look for as per your requirements. Please note the missing ":" in the set command.

    Reversing the order of the alphabets would be a better option since the cd drive letter usually takes on a character after all the volumes are mapped. In this case there would be no errors in the event of finding a similarly named file in the root of a local volume.

    If you create your volumes after installing the OS it creates another problem, i.e. the volumes will be assigned letters following the cdrom which might turn out to be "d:". So what I usually do is assign the cdrom drive letter "W" from run_once file using diskpart. On a single cd drive systems this invariably is volume 0.

    I use a utility called wineject which takes on simple switch. The code is ...

    wineject -open w

    sleep 10

    wineject -close w

    wineject & sleep.exe of course are external files & freeware.

    I do recommend thern to use the "for... blah blah" to detect the drive (although I think WPI has a separate method to detect the drives?) but I don't really see what you're doing afterwards. :D

  12. Try to unpack a regular AutoIT script with upx -d and run it.

    And then try to unpack CDSwitch and it will give you the error metioned above.

    So I can say that CDSwitch is a little different :angel .

    =) That'll teach you naughty hackers! XD

    Well I don't know what I'm doing wrong but It doesnt work.

    I downloaded only the zip with cdswitch but it doesnt work either.

    The file is clean so I dont guess it was a virus

    Any idea?

    Maybe the sintaxis is wrong but I'm testing the example.

    Oh! I know maybe the mistake. Do the program work without wpi?. Because I need launch cdswitch before wpi starts the applications are in the second CD the first one is just XP

    See ya!

    Wrong syntaxes don't give that error, heh (CDswitch pretty much won't do anything then). Second, it's not wpi-only. Third, what happens when you execute "cdswitch test 1" in your normal windows environment?

  13. CDSwitch is a little different from other executables written in AutoIT. Its special "feature" is that once you unpacked it, it won't work again.

    I won't write a longer reply because I don't want my ideas to be used to decompile other programs.

    What the hell is that supposed to mean? :P

    Great program, it was I needed but I've got a problem. When I run the appz, this show the next message "Unable to open the script file".

    As said by the people before me, rather a download problem. If it remains everytime, try downloading a different version (either the one supplied with WPI, or the one from the main mirror [see sig for that one]).



×
×
  • Create New...