Jump to content











Photo
- - - - -

New mkISOfs script v009


  • Please log in to reply
61 replies to this topic

#1 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 11:52 AM

mkISOfs Script v009: download


Log of changes:
-Now the script copies projectinfo.ini in the default iso.
-It makes the iso bootable from RAM with PicoXP
-If the user selects to boot from RAM , the script deletes the first ISO from the ISO folder.
-It lets the user select whether to run mkisofs silently or not
-It deletes some files that were created in the past in the target folder by this script. ( Thanks Proton for the idea)

Screenshot:
1.jpg


Smiley

#2 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 01:28 PM

Very good job. I like where it deletes the ISO if you create a RAM iso.

Both Standard and PicoXP Boot as A regular ISO now. Standard Still boots fine with Boot from RAM ISO. The Pico XP still reports that it cannot fine the ramdisk.sys. At least the normal one ISO works on PicoXP. Can you make it extract the ramdisk.sys from RAMDISK.SY_. Remember you said that it could be compressed but it doesnt seem to work with picoXP. It just works with the standard right now. I point the RamBoot to the folder that contains setupldr.bin, and RAMDISK.SY_. Which you said would be fine.

This is using the new PicoXP Script which was updated by psc but taken back to the old one.

#3 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 13 September 2006 - 01:43 PM

mkISOfs Script v008 beta 1 : download


Log of changes:
-Now the script copies projecttinfo.ini in the default iso.
-It makes the iso bootable from RAM with PicoXP (untested)
-If the user selects to boot from RAM , the script deletes the first ISO from the ISO folder.

Please test and post your results
Smiley


My test results with PicoXP and different source CDs

Source XP SP2 German:
Direct ISO :P
RAM ISO :P

Source XP Sp2 English:
Direct ISO :P
RAM ISO :P

W2003 SP1 English:
Direct ISO :P
RAM ISO


W2003 SP1 German
Direct ISO

RAM ISO


I suggest: Apply your change when OS is XP. And the current version of PicoXP cannot be booted from RAM.

Peter

#4 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 01:53 PM

My test results with PicoXP and different source CDs

Source XP SP2 German:
Direct ISO :P
RAM ISO :P

Source XP Sp2 English:
Direct ISO :P
RAM ISO :P

W2003 SP1 English:
Direct ISO :P
RAM ISO


W2003 SP1 German
Direct ISO

RAM ISO


I suggest: Apply your change when OS is XP. And the current version of PicoXP cannot be booted from RAM.

Peter


Using XP source it works because the create iso script copies the ramdisk.sys . I'm going to fix it to copy also when using W2003 as source :P

#5 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 02:03 PM

Beta 2 released! I hape it fix it. (See first post)

#6 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 13 September 2006 - 02:26 PM

Now W2003 English works both Direct and RAM ISO. :P

But both W2003 German have the same blue screen: :P


What's with greek?

I'm rather sure that this is not a 'feature' of your script. This is based deep in PicoXP. And I'm going to find out what happens.

Peter

#7 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 03:56 PM

Now W2003 English works both Direct and RAM ISO. :P

But both W2003 German have the same blue screen: :P


What's with greek?

I'm rather sure that this is not a 'feature' of your script. This is based deep in PicoXP. And I'm going to find out what happens.

Peter


are you sure that it isn't a problem with create iso script? If not, i'll release it as ready :P

#8 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 06:06 PM

Now it creates a good Pico XP RAM ISO but not a Regular Pico XP ISO.

Same error about Ramdisk.sys when creating a regular Pico XP ISO and running it.

Standard RAM ISO and Regular ISO are fine.

Log Regular Pico XP ISO



#9 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 13 September 2006 - 06:11 PM

are you sure that it isn't a problem with create iso script? If not, i'll release it as ready :P


Yes, I'm sure.

The script has to distinguish between XP and W2003, but it really does not have to handle W2003 English and German differences!

Peter

#10 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 06:14 PM

Now it creates a good Pico XP RAM ISO but not a Regular Pico XP ISO.

Same error about Ramdisk.sys when creating a regular Pico XP ISO and running it.

Standard RAM ISO and Regular ISO are fine.

Log Regular Pico XP ISO


What source do you use? Can you post a screenshot?

#11 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 06:18 PM

Yes, I'm sure.

The script has to distinguish between XP and W2003, but it really does not have to handle W2003 English and German differences!

Peter


First i'm going to examine TheHive's issues and afterwards i am going to release it

#12 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 06:22 PM

@TheHive: Have you cleared your target before testing?

#13 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 06:31 PM

I tought it was an automatic Target Clean up on PicoXP also. And it seems as it does clear it when it run the PicoXP and its running the Scripts. I also tried a manual clean up and I still get the error message.

#14 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 06:34 PM

What source do you use? Can you post a screenshot?

#15 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 06:39 PM

Posted Image


Posted Image

#16 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 06:43 PM

I mean screenshot of the error . What language is your source?

#17 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 06:52 PM

lol! English.

Posted Image

#18 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 06:56 PM

Hold on one sec. I just downloaded the latest WinBuilder_SandBox20060913_02.zip and testing and it seems to be working and booting. Let me test some more.

#19 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 07:09 PM

Dowloaded the latest WinBuilder_SandBox20060913_02.zip, and just replaced the mkISOfs Script v008 beta 2 and replacing the location of where the RAMboot files directory is.

All Seems to work. The Regular PicoXP ISO and RAM PicoXP ISO. ALso both RAM and Regular Standard ISO.

:P :P

#20 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 07:15 PM

Please read this

#21 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 13 September 2006 - 07:17 PM

@PSC: I can't publish it now because i am realy busy:D

#22 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4199 posts

Posted 13 September 2006 - 07:18 PM

I had read that post when you posted it but I had not comment to the thread. :P
Thats what gave the idea to check to see if there was a new one available. :P

#23 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 14 September 2006 - 08:51 AM

Good news first:

Now (with beta2) everything is running:

XP SP2 German and English
W2003 SP1 German and English
Both with Standard and RAM ISO.

Reason was:
In my slipstreamed W2003 English there was besides the standard MSVCRT.DL_ an old MSVCTR.DLL which I copied.
In my German version there was the standard DL_ only, so failure.

(fixed)

Now the bad news:
Build a project with RAM ISO and run it under Qemu.
The run it again. You get the error:

#103 [Failed] DirDelete - Failed to delete directory [%BaseDir%\Projects\PicoXP\Target] 1 error(s) while processing.

The target is really not cleaned, but can be deleted manually.

@smiley: can I do something to help with 32bit driver?

Peter

#24 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 14 September 2006 - 10:56 AM

@smiley: can I do something to help with 32bit driver?


No , the only needed is to compile it (i think). You can help if you can compile it :P

#25 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 14 September 2006 - 11:06 AM

No , the only needed is to compile it (i think). You can help if you can compile it :P

Which compiler?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users