tomasz86

A new daily of UURollup-v11 is ready. I found out that there's a problem with XP's cmd.exe. While it does work, it also consumes extreme amounts of RAM compared to the original one (around 1000% more to be exact). Therefore I've decided to remove it from UURollup. UURollup-v10 is unaffected since there's no cmd.exe included in it.

What kind of machine are you trying to run the program on?

Strange... It just works here. No errors at all.

The official XP drivers (with a modified INF file) should work with the unofficial kernel. That's why I mentioned UURollup-v11 daily. The modified versions are for stock Windows 2000.

Thanks The short one CD.> new_empty_file_name is really nice.

And x Etron USB 3.0

This seems to be the newest one: http://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_xp.aspx I'd suggest trying to install only the driver through the INF file without CCC and other software.

Something is different between 2K and XP in this matter. When I do: COPY/B NUL 1.txt an empty file gets created when using cmd.exe from Windowx XP but when doing the same with Windows 2000's cmd.exe: The parameter is incorrect and no file is created. In Windows 2000 it's necessary to use: COPY NUL 1.txt to create an empty file while in XP the switch doesn't matter.

Someone just needs to modify the INF file. The old driver is for older chipsets.

For AHCI you probably need to use a new driver. I'd suggest that you install the latest daily release of UURollup from here and then you will be able to use the official XP drivers (with a modified INF file) which you can download from here. It's not the latest version but should work nevertheless. Same thing with AMD Graphics drivers but I've got no working one at the moment.

I think that all of them (SP1a, SP2 and SP3) remove Java. Also technically SP3 seems to require just SP1 (not SP1a): MinNtServicePackVersion = 256

No problem. Please let me know in case there are any issues

Right. My mistake I'm wondering why it's not allowed. Do you know anything specific about it? I think I'll try to modify the update.inf and try to install it in XP RTM and see what happens.

Service Packs are cumulative. No need to install any previous versions

Has anyone tested the last daily of UURollup-v10e? If there are no problems with the new wtsapi32.dll & winsta.dll I'm going to release this version at the end of March.

@ Slipstreaming isn't an ideal solution. Sometimes you get an old computer with Windows already installed which hasn't been updated for a LONG time. I had such a situation some time ago and it took a whole day to install SP3 and all the remaining updates from WU. Of course it was just a Pentium III with a slow HDD but still...

I've been working on a script which at the end should make possible adding new updates to Service Packs. My main target is of course Windows 2000 but it shouldn't be very difficult to modify it a little bit and use for Windows XP and 2003 too (at least the x86 editions). Another possibility is to prepare an update rollup which is much easier than compiling a new Service Pack.

Have you tried using other browsers than the default one? You may also want to check the Tapatalk application from the Android Market.

It can be but requires manual registry modifications. The problem is only about switching from IDE. You don't need to modify anything if you're switching to IDE or even between SATA and SCSI as long as the required drivers have been installed in advance.

There are some SCSI drivers integrated but that's it. No SATA

I've managed to install it using the latest daily release of UURollup-v11 but one of its services doesn't work and the application itself also doesn't start (the process is running in background but no window is shown on the screen)

I have uploaded two new daily releases of UURollup: The first one is a new release of UURollup-v11 which contains all of the new changes introduced by blackwingcat in his latest kernel v2.3a together with wtsapi32.dll / winsta.dll from XP SP3. The second one is a new release of UURollup-v10 which is called UURollup-v10e. As it's still unknown whether and when UURollup-v11 will become stable enough to be "officially" released, I'm going to keep supporting the v10 line. By supporting I just mean fixing bugs. Sice UURollup-v10d also used wtsapi32.dll 5.0.2134.4 which prevents TeamViewer from loading on startup I've added wtsapi32.dll / winsta.dll from XP SP3 to it too. I've also uploaded a new HFSLIP_ia.7z package featuring the latest daily of UURollup-v11.

Are you sure? I think that it's a little bit more complicated Kernel 2.3 + wtsapi.dll 5.1.2600.5512 (XP SP3) Kernel 2.3 + wtsapi 5.2.3790.3959 (2003 SP2) WTSRegisterSessionNotification is present in both of them. Is there any reason not to use XP SP3's wtsapi32.dll?

@ Yes, while I do the dirty work when it comes to preparing and compiling the unofficial packages, Tommy helps me a lot in testing and improving them You can think of him as the main tester of UURollup.

There's no error message. It's just that the TeamViewer's two other processes (TeamViewer.exe and tv_w32.exe) don't start on boot. They will start if you uninstall the kernel or just replace wtsapi32.dll with its original 2K version or use the one from XP SP3. You can clearly notice it as normally there should be a TeamViewer icon in the system tray but there's none when your wtsapi32.dll is used Kernel 2.3 + wtsapi32.dll 5.0.2134.1 Started processes: TeamViewer_Serv TeamViewer.exe tv_w32.exe Kernel 2.3 + wtsapi32.dll 5.0.2134.4 Started processes: TeamViewer_Serv The two others are missing. What's interesting is that TeamViewer works with XP SP3's wtsapi32.dll but doesn't with 2003 SP2 wtsapi32.dll. The processes also don't start on boot when 2003 SP2's wtsapi32.dll & winsta.dll are used. @Tommy Thanks a lot for testing