Yeah, Happy new Year. I'm usually miserable at New Year, but we're going out in a bit to celebrate. Have a good night, everyone.
Still no wiser about the NIC, only that the newest (PCIe Gb family) driver causes lockups, the older one that we have works for the most part. Following that logic, an older one might do the trick, if it's down to firmware of some of the Jogglers. I feel like we're going round in circles... Might be a glitch in The Matrix, but I'm sure we've had this same conversation before!
We probably have, but its a bug that's annoying alot of people lol, I personally only utilise the WiFi on my joggler, but would like to get it fixed for others
Fullscreen squeezeplay windows, server 2003, foshiz mini v1 and v2, (and a few broken builds) :P so far.....
more to come!!
I'm guessing that the whole network thing could be something like a "tweak" to the "inf" files for the drivers of the Realtek NIC similiar in fashion to the sound driver modifications.
The older drivers had a configuration txt file for some adjustments. The firmware modifications posted on Realtek related to a write to the rom for booting et al but little else documentation exists for anything else non related. That said it would be easy to brick the firmware on the integrated NIC should some mishap occur.
There is a definitive difference in the newest #5 Joggler that I have been playing with; as Mevi said it's probably a difference in the firmware pieces of the integrated NIC card. Sometimes just leaving it powered off / disconnected NC for say 30 minutes or more is enough to get it to work again or out of its D3 state. I remember with Joggler #1 seeing the error 10 coming up and making the assumption that just changing the values of the legacy Realtek drivers was making it work; don't really know though if that was what was occurring.
- Pete
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
danfoshizzle wrote:will also contribute mevi, we may have slightly different ways around things lol
Yeah, of course - it's all good. I build mine in VirtualPC, VHDs and use minitools to image the drives. I've built all mine from TinyXP or OEM disks. I'm sure someone else will have a way of doing things that is different again!
Hello everyone...
Can someone please point me to working Sound driver so internal speaker to work and Audio out...
And also I can't get windows xp to boot from USB HDD I always get ntldr error...If someone has booted from USB HDD can please explay how it is done ?
How many partitions ? or everything can be stored into one fat 32 partition ?
You need a fat16 or fat32 primary partition of about 200MB, with the EFI files in (too small and it won't boot). The second XP partition needs to be NTFS primary ACTIVE partition. If you download one of the builds of Windows Server 2003 or XP Pro SP3, you will see how it works. If you are making a build of your own, you will need USBoot so that XP will boot from a USB drive. Lastly, you will need the replacement NTCOMMAND.COM, NTLDR and VGA.SYS. Boot.ini will also need to point to partition (2).
There is more to it than that, so we plan to write up a proper instruction guide.
danfoshizzle wrote:shutdown at 11 seconds, both of these times with no ewf, will post ewf results in a while
Whoops, no excuse for that goof... The number of times I've copied those files over..
Holy crap, 11 seconds to shut down. That's quick. Boot times are a pig, even with XP stripped back and with minlogon, I can't get any faster. Boot times of hdd vs flash don't seem much different either.
lol
