Recommended Posts

Okay...1.0.28 works fine but i need to confirm one thing here....As soon as it detects the 266Mb Service Pack 2...it displays 5.1.2600.2180 (Pre-SP2). This is false syntax on the part of the application ??

Okay...1.0.28 works fine but i need to confirm one thing here....As soon as it detects the 266Mb Service Pack 2...it displays 5.1.2600.2180 (Pre-SP2). This is false syntax on the part of the application ??

Yes, this is an error in the application, a bug. It is fixed in version 1.0.29, but since it won't let you install SP2 because of the "Wrong OS" error, then you'll have to live with 1.0.28! At least until they fix this bug (which shouldn't be long).

ok, I'm sorry, I thought he was on vacation and wouldn't fix it for awhile. Thanks DJ Prem, I'll be patient. :cool:

Actually he IS on vacation. :laugh: He had just stopped in for a couple hours and left again. When he gets back he'll release a fix/new version. :yes:

Thanks for the update...where did he go/going for vaction?

Well, I live in Athens (where most of the events are held). As far as vacation is concerned, I rarely visit our islands (I did that some years ago). Instead, I stay in Dilesi/Oropos (I bet most of you will have a real hard time pronouncing this!!). It's a 30 minute drive from Athens (Average speed 150 km/h). Since I never take any PCs with me, the only way to do anything PC-related is to... well... take a vacation-break!

/Raptor

You can add scsi etc drivers easily.

In the step AFTER the SP2 is installed in your XPCD (as an example) directory but BEFORE you have nlite go to work on the reduction....simply do GreenMachines example of how to add drivers like Sil3112 sata/sataraid to the WinXP disk. Then run the next step on nlite, pulling out all the crap from the XPCD folder.

This seemed to work fine for me.

I figured out the "disk read error" issue:

With XP on fresh formated drives, you need to go into the bios and RE-DISCOVER the drive. Then install XP. otherwise on the first reboot there is some really funky NTFS conundrum that occurs. I tracked this down on the error, and lots of people re-installing XP on new upgrade drives, etc have this happen. Later after clearing CMOS or some other thing it suddenly works. Well, its because the bios reports disk info in correctly and snarfles the WinXP setup on the first reboot....something to do with boot sector switching from FAT32 to NTFS...all in WinXP's hands..the user is never aware of this activity.

Just thought I'd pass this along....it was using the VMware trial that sent me down this path.... the VM's all worked perfect, but the real HDisk screwed up.

Nice Proggy raptor!!!

Nice app...but I dont know howto burn this cd.

Which app? :s I have Nero and Pinacle...

And what options do I use...last time, Nero burned, and explorer said the disc had nothing on, but space had been taken up. It wouldn't boot either.

Any help for burning and hwat options and a howto?

Nice app...but I dont know howto burn this cd.

Which app? :s I have Nero and Pinacle...

And what options do I use...last time, Nero burned, and explorer said the disc had nothing on, but space had been taken up. It wouldn't boot either.

Any help for burning and hwat options and a howto?

open Nero and cancel out of the window that opens. Select recorder and burn image. Select the image that AutoStreamer made and click burn.

I have tried to research a fix for the Runtime error, but I haven't found anything yet. I get the following error when clicking on next from the initial screen. This is with the current download available from the link posted earlier. 1.0.29

AutoStreamer.jpg

The I looked at the threads talking about the DAO pieces, but they didn't help.

http://www.google.com/search?hl=en&ie=UTF-...ntime+error+429

Anyone have any ideas what is causing this error?

My friend used this app to create his iso and his image fits to a cd. The one I created from nLite is 800MB and the one I created the old fashioned way was 900MB. Just a weee bit to large for a cdr.

Thanks!

Hmmm.... spoke too soon.

Seems Slip'd SP2 disks have potential issues when you go to actually USE them on a new or upgraded system.

I did a test.....fingers tired.

WinXP Home retail, WinXP pro OEM, WinXP pro Corp gold's to start with....all install perfectly.

Made a SP1 and SP2 version of each of the 3 OS's....did it 3 ways;

A) by-hand (folders/copy/update commandline)

B) Autostreamer

C) nLite

SP1 and SP2 versions all install perfectly under VMware....so we make CD's.

Thats right... 18 CD's, $.10ea so why not, I wanted to test this out, since I had trouble.

Gold's and slip'd SP1's all install correctly without incident...using a 80G/8 Seagate IDE as a mule. I've used this as my IDE backup with Win2Kpro installed for years....to cover/setup/maintain/resue my sata raid0 array.

Well, then comes SP2....all fail. That's right all 9 iterations of SP2 fail in the same manner.....

Setup installs correctly, copy's files, etc but when it reboots to actually then BOOT off the new SP2 based hard drive it generates "disk read error".

Now if I use any slip'd SP1, then use the 266MB SP2 Admin servicepack.... no problems, works like a charm.

Tested on a different system, got the error once, but cleared it up with a visit to the bios and a "re-discover" of the hard disk by the bios. But on the main system...DFI Infinity, 6/19 bios, it was a no go regardless of anything I could do. All the usual suspects were covered....this is NOT a hardware problem, as SP1 is flawless, as is SP2 as a servicepack, on the same hardware.

Something about SP2 as an actual completed CD is not interacting with the bios correctly, in getting the info about the disk to the OS.

Ill move to SATA and try using sata instead of IDE as the disk channel and see if SP2 does better.

It's something that looks like a BIOS-vs-SP2 issue, and so some systems will have issues and some wont. The PoS Intel fake PC that VMware pretends to be has no issue :D And my NF7-S system has only a slight issue but it was able to get over it.

Since noone is selling SP2 WinXP's yet, and only the few/brave do the whole slipstream thing, its not a big deal yet. But I predict it may be a real issue down the road. WHAT did they change that is causing this? Hmmm :angry:

Thought I give a heads up.... nice proggy Raptor!

Hi, I have a CD with czech version of Windows XP Corp. I tried to open CD and ADD SP1 update, which I have downloaded. When I try to open CD, I obtain following message:

Error.jpg

Then the AutoStreamer is closed and in its directory there is generated a new "temp.bat" file, which contains:

@echo off

expand "F:\I386\NTOSKRNL.EX_" -F:ntoskrnl.exe "D:\INSTALACE\WINDOWS XP UPDATE\JIN?\AutoStreamer\AutoStreamer 1.0.29\NTOSKRNL.EXE"

I know there is probably problem with supporting my language version, but is it possible to do something with that? :rolleyes:: I would like this utility very much :)) . If there is problem with that "NTOSKRNL.EX_" file on my CD, I can send it by email to creator of AutoStreamer. Thanks for reply and help here or on my email: [email protected] :yes:: :yes::

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

    • No registered users viewing this page.
  • Posts

    • Formatting would be awesome if fully customised and then roll out the settings as a company wide standard.
    • I just want to know why the volume control feature in the browser version keeps appearing then disappearing, here today - gone tomorrow. Now it's gone again. Annoying as hell.
    • When you have only lies and blood libels to present, you've lost. And how hard is it for you to look up BBC and AP? You hate Jews, just admit it.
    • This article does not make sense and it’s very evident, the bug wasn’t confirmed to exist, because the application itself runs on editions of Windows which make it impossible to run Hyper-V VMs on, “Basically, Claude Desktop on Windows spins up a 1.8GB Hyper-V virtual machine if you use Claude Cowork or agent mode even once.”, suggests the bug is caused by something else otherwise it would only happen to users with the capability of running Hyper-V VMs and that’s only if Hyper-V was enabled which is by default not enabled. The true issue is that the author who reported the bug used the incorrect terminology, it’s actually a container, not a VM that is being started by the way. There were users on macOS reporting the same issue, Hyper-V, doesn’t exist on that platform obviously. Every single user who confirmed the problem in the last week was either using macOS making this issue impossible to be relevant to them, or was a comment talking about WSL, which the author indicated 3 months ago was disabled.
    • “To prevent hallucination issues and keep the database clean, the platform uses a multi-agent verification loop to check code quality.” - This absolutely isn’t happening. ”Before the massive rise of LLMs, which tanked its traffic by about 50% over the last couple of years, Stack Overflow was the go-to website for millions of programmers seeking coding solutions.” - It still is trusted, because the community of users, blocked other users from submitting false and misleading answers generated by AI agents that can be convinced something it generated is actually incorrect even if it’s actually correct. The company itself doesn’t know what it wants to be so it keeps trying and failing to introduce AI features to the platform. This effort will also fail, already submitted one successful poison pill, look forward to generating more.
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      524
    2. 2
      PsYcHoKiLLa
      211
    3. 3
      +Edouard
      160
    4. 4
      Steven P.
      98
    5. 5
      ATLien_0
      83
  • Tell a friend

    Love Neowin? Tell a friend!