Recommended Posts

So here it is! I've been working on this one for some days now, and I think it's OK to show some very early screenshots... well - screenshot :p unless you wanna see more :)

AutoStreamer is a slipstreamer which work in two modes:

1. Original Windows CD mode

User inserts original Windows CD, specifies a valid Service Pack file and a temporary folder and AutoStreamer will:

Copy CD files to temp

Slipstream to temp

Generate bootable ISO from temp

Delete temp

2. Local share mode

User specifies local share folder and Service Pack file... In this case, AutoStreamer will:

Slipstream to local share

Generate bootable ISO from local share

AutoPatcher is able to detect if the Service Pack file you specify is a valid one (i.e if you insert a WinXP SP1 CD and pick Win2K SP4 file it wont accept it... or if you insert a WinXPSP2 CD and specify WinXP SP1 file it wont accept it)

Enjoy

/Raptor

post-89-1088530305.jpg

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/
Share on other sites

Nice screenie. Now that the secret is out...let the questions begin.

Will your program allow Slipstreaming XP SP2 on a non-XP machine? I'm not sure if this is an RC issue or if RTM will fix it, but the slip blows up near the end, unless you are doing it on an XP machine (see image)

Suggestion - since it is "Autoptacher's Little Brother", you should include a few un-attended "prep" options:

-Add a prompt to look for a copy of AutopatcherXP 4.x and copy it and any $OEM$ folders to the TEMP CD directory

-Delete unnecessary I386 folders to make room on the CD

I hate to already hit a program still in development with add-ons/issues, but if you're in the coding phase still, you might save any massive response AFTER you release it. Plus you want to outdo N-Lite right? (the project of the evil doers M_S_F_N :devil: )

Keep up the good work Raptor! :D

EDIT: forgot the error image

post-89-1088532833.jpg

Edited by paratrupr
Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2384785
Share on other sites

Right. It "slips" service packs into the original Windows CD package so a complete reinstall of XP would already have SP1 (for example) applied. AutopatcherXP adds additional value to unattended installs by picking up where SP1 left off with the most current patches and hotfixes released after service packs, since you can't slip those individually.

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2385147
Share on other sites

It sounds like it is only an XP service pack slipstream tool, and does not incorporate APXP or unattended installs. I was merely suggesting Raptor throw those options in, which could assist SlipXP - not taking anything away from Shify who is working on a newer version.

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2385201
Share on other sites

It sounds like it is only an XP service pack slipstream tool, and does not incorporate APXP or unattended installs. I was merely suggesting Raptor throw those options in, which could assist SlipXP - not taking anything away from Shify who is working on a newer version.

No doubt AutoStreamer looks nice but it does look like (intended or not intended) a replacement for SlipXP. I would doubt the addition of both apps in the AutoPatcher package. My money would be on AS being included which I think would effectively kill off the SlipXP project.

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2385238
Share on other sites

Nice screenie. Now that the secret is out...let the questions begin.

Will your program allow Slipstreaming XP SP2 on a non-XP machine? I'm not sure if this is an RC issue or if RTM will fix it, but the slip blows up near the end, unless you are doing it on an XP machine (see image)

Suggestion - since it is "Autoptacher's Little Brother", you should include a few un-attended "prep" options:

-Add a prompt to look for a copy of AutopatcherXP 4.x and copy it and any $OEM$ folders to the TEMP CD directory

-Delete unnecessary I386 folders to make room on the CD

I hate to already hit a program still in development with add-ons/issues, but if you're in the coding phase still, you might save any massive response AFTER you release it. Plus you want to outdo N-Lite right? (the project of the evil doers M_S_F_N :devil: )

Keep up the good work Raptor! :D

EDIT: forgot the error image

there's nothing i can do about that, unless i start writing my own slipstreaming procedure...

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2385285
Share on other sites

Excellent. As far as the error goes, at least be prepared for a customized error message letting the user know the slip failure could be due to outdated VB Runtime files. Just a suggestion.

Regarding SlipXP: Shifty needs to release some details to the project, as you two might be able to combine efforts.

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2385359
Share on other sites

That's the strange thing people are noticing...you CAN slip XP Service Pack 1 on 2000, I've been doing it since it came out. It's just recently emerged in the betas and RC's. Some people are speculating that the MS Development team hasn't thrown all of the slip capabilities in yet, so we will have to wait for RTM (however, as most know, you can slip SP2 if you are using XP - I have done this as well and it works fine).

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2385417
Share on other sites

This project was initiated by me talking to Raptor about XPCreate and nLite last week. The guy that makes XPCreate is not a very nice person and I've heard of problems with nLite. I have been looking for this type of tool for months now and really didn't want to promote MSFN. I really wanted to find a Neowin project that would help my project out and to promote Neowin more. So like I said I talked to Raptor about it and asked for suggestions. He said it should be easy to create something like that. The really awesome part about this is I just suggesting this project with Rapor and within an hour or two he sent me a beta to test!! We've been working on it for the past week and it's coming along quite well. I just wish I knew how to code so he didn't have to do all the work!! I have helped him a little though.

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2391099
Share on other sites

Yup, SteelTrepid is right. Hopefully this will make it much easier for people looking into the Windows Ultimate Boot CD to get the requirements made easily before proceding (since it's based off of BartPE, it needs Win XP SP1). Should help out the project a lot as well and thanks so much to Raptor for doing this. :-)

Link to comment
https://www.neowin.net/forum/topic/184212-autostreamer/#findComment-2391608
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • After watching the Apple event earlier this week it is quite the contrast. Apple is going back and tweaking the code to make things more efficient in may areas of MacOS. Windows is boosting your electric build to hide their issues.
    • It is silly there is no simple way to check whether this profile has been activated. CFRs are normal, but trying to even hide the fact if it's on / off seems silly, especially for something so user-facing. Surely Microsoft is "proud" of their engineering efforts on this one and ought to display it somwhere in the GUI.
    • Many Linux distros are not known for excellent battery life, so I'm not sure that is the best example. A more apt example may be Apple, but Apple's CPUs are simply far more efficient than Intel & AMD at single-threaded tasks like these, so "boosting" is not as power-hungry and less heat-inducing. Not to mention Apple will hardly engage P-cores for basic UI tasks; they use a pretty complicated QoS scheme to only activate P-cores for more serious workloads like HTML / JS execution or decompression or application launch. Microsoft is (smartly) doing it for launch, but also for UI tasks, which is the more nonsensical part: why ... do Windows 11's UIs need modern CPUs to boost? It should load so quickly that there's not even time for the CPU to boost.
    • I've not seen any controlled testing and, judging by Microsoft's mentality, within a year, they'll have added so much more bloat, it'll undo any perceptible latency benefit and we'll have boosted the CPU clocks for nothing.
    • It depends: heat soak is a thing. Initially on cold boot-up, the heatsinks & heatpipes are at ambient temp. After heatsinks & heatpipes warm up (through normal usage), they don't immediately cool to ambient temp when the load goes away. So their baseline is higher and the trigger point for fans is much less stress. Add a few more CPU spikes → it's too hot to stay at the same fan RPM → fans get triggered to start up up much sooner / get triggered to ramp much more quickly.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      74
  • Tell a friend

    Love Neowin? Tell a friend!