Recommended Posts

There are threads all over the place that describe this very issue, but this thread goes back to July where Raptor, who created Autostreamer, stated the likelihood of this.

When he gets back from vacation he will no doubt fix this. It misreports it, but the slip works fine.

I belive it was developed in XP, but I don't recall Raptor telling me that it had to be run from XP. I really wish he would get back from vacation soon. There are so many little issues that I cannot answer because he didn't give me all that information while we were developing it. I'm glad he gave it the capability of slipstreaming 2000, XP, and 2k3...but your question still bothers me (not to mention the runtime errors other have reported).

I mentioned this a few pages back, here.

If you slip SP2 outside of Autostreamer using update.exe you get the error message shown below. As of today, I have yet to find a fix for it, although it is not an AS issue; must be a Microsoft thing.

Have to do it in XP...

post-89-1092367638.jpg

Ok like many b/4 have said this is a great utility. BUT, I am having a slight problem that when I try to create the .iso file it is only creating a file that is like 1.31Mb. Definantly not a good .iso file for this. I have tried multiple times. I am using an XP Sp1 CD for the source and the Sp2 file that I downloaded from the M$ webstie. Any suggestions or hints on this. On the first screen all of the information is coming up as many other have shown with their screenshots but for some reason it just won't make a proper .iso for me.

NOTE TO ALL: If your Dell CD fails to slipstream it's not because it's a restore CD, it just has some hotfixes slipstreamed in a funky way and it needs to be cleaned up. ...

And how does one go about doing this?

Has anyone come up with a fix/workaround for the run-time 5 error?

I'm still wanting to know the same thing -- I think it's related to the point I quoted above.

I'm still wanting to know the same thing -- I think it's related to the point I quoted above.

Got the most recent Dell OEM CD I could find (July 2003). In the I386 directory do the following:

1. Delete the directory "SVCPACK" or "UPDATE"

2. Delete the file "SVCPACK.INF"

3. Delete all files named "Q??????.EXE"

4. Delete the following lines in "DOSNET.INF":

[OptionalSrcDirs]svcpack

Now you should be able to slipstream it

When I click next for the first time I get this error

Run-Time error '429':

ActiveX compentent cannot create object

I also can't get past the first screen... Press "Next" and the same error message appears.

I am logged on as Administrator with FULL read/write permissions.

I am not missing the msvbvm60.dll. In fact running "FileMon" shows that AutoStreamer is finding everything it needs.

I have tried re-booting and closing down all my background apps.

There seems to be at least four of us now (maybe more) with the same problem.

Any advice would be welcomed. :huh:

Running WinXP Corp. SP-1 with all Microsoft Updates.

is developer support for this already dead? you'd think with the excitement and amount of feedback its getting, it would be getting alot of attention for further development and fixes, but it seems to have stagnated already

Raptor is away on vacation. He will be get back on the bug issues and updates when he returns

When you get your Error 5, are you running AS from your desktop?? I've seen a few people with this error and it was fixed by running it from a "real" folder on their system. I'm hoping this is what is causing error 5, hopefully I can help figure out the others also.

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

    • No registered users viewing this page.
  • Posts

    • I agree, but that's the popular online opinion about them, so I followed it. I do think they have their point, no matter how combative they sound most of the time.
    • M$ can bring whatever the hell it wants, and then guess what's not installed in my Mac.
    • Windows 11's big performance boost is finally available for all by Taras Buria Over the last few months, Microsoft has been very busy fixing Windows 11 with features that users have been asking the company for a long time. An upgraded Start menu, the ability to change the taskbar position, new Windows Update features, and plenty more. However, not all changes are visible on the surface. Some exciting upgrades happened under the hood, and one of those upgrades is now available to all Windows 11 users. The so-called "Low Latency Profile" is a special performance mode that aims to make Windows 11 snappier and more responsive. It boosts the processor clock speed to its maximum for a brief moment when rendering user interface elements or launching apps. As such, apps launch faster, and things like the Start menu or quick settings appear on the screen faster, although some are sceptical about it. Microsoft is not sharing many details about the new profile. The official release notes do not even mention it, with Microsoft only saying that the update "accelerates app launch and core shell experiences such as Start menu, Search, and Action Center." Also, you may need to enable it manually, as new features are rolling out gradually. Here is how to do it: Download ViVeTool from GitHub and unpack wherever convenient. Navigate to the folder containing the ViveTool files with the CD command. For example, if you have placed ViveTool in C:\Vive, type CD C:\Vive. Type vivetool /enable /id:58989092 and press Enter. Restart your computer. After restarting your computer, launch Task Manager or any other hardware-monitoring software and check the processor clocks when opening the Start menu, Action Center, and more. Your processor should spike to its highest possible speed and then return to lower clocks. In addition to Low Latency Mode, the June 2026 Patch Tuesday update delivers additional features, such as multi-camera mode for apps (several apps can use a single camera stream), shared Bluetooth audio, improved Task Manager, and more.
    • I agree, especially with newer versions of MS Office supporting ODF documents, there isn't even a compatibility argument to be made. It should default to ODF on a clean install, with admin configurable options to make MS Office the default if that is desired.
    • Are they on crack at M$? Surely living on an alternative reality? A good dump of mine would run faster down the toilet if I did not flush it. But still looks better than this pile of slop. By the way, did they also comment on what's the next "functionality added"? Maybe you can improve it if you add even more stuff to this vomitware.
  • Recent Achievements

    • Week One Done
      FBSPL earned a badge
      Week One Done
    • One Year In
      Jim Dugan earned a badge
      One Year In
    • One Month Later
      Tommi118 earned a badge
      One Month Later
    • One Month Later
      sjbousquet earned a badge
      One Month Later
    • Week One Done
      sjbousquet earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      PsYcHoKiLLa
      196
    3. 3
      +Edouard
      155
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      69
  • Tell a friend

    Love Neowin? Tell a friend!