Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sneakyghost

  1. i can say this: On an Acer Aspire One netbook i had no trouble integrating every single driver. half of all those drivers where intended for Windows XP since Acer does not provide any support for drivers other than linux and xp. The other half where vista-drivers. i checked the display-driver which turned out to be windows display driver model 1.0 whereas windows 7 requieres WDDM 1.1 i believe. not sure though. The driver was still accepted without any complaint. This might very well change after the beta or release candidate stage. I am not sure if the final product still takes any driver without signing and such. oh yes and before i forget this: i am talking about the 32-bit variant. On my Desktop i have the 64-bit version and there i cannot put in unsigned drivers. keep this in mind.
  2. Most things i tested on win7 7077 x64 are already listed here. the ones i didnt see are below: xFire latest release by date of post works well. Unreal Tournament 3 patched to 2.0 works well. ATI Catalyst 9.4: driver ok, CCC does NOT work. Realtek Azalia: Vista driver installs fine but won't install Control Panel - copied over all necessary files from Vista 32 Bit install and voilá it works... Office 2007 ok on Desktop, not on netbook (won't start, needs to much ram). peerguardian latest vista-alpha release does not work - it already has probs on vista and development has stopped. Trillian Astra beta works well. Easy BCD works well. VLC works well. Creative X-FI drivers (Beta for Win 7) work well. Daemon Tools 4.30.305 include SPTD Driver 1.58 and install and run on Windows 7. this for now...
  3. i did install it to SSD as mentioned and the install takes very, very long but it works really nice. I found out that i have trouble now running office though. the current config with 512 Meg of ram wont allow office to start because windows 7 even as reduced as it is takes already approx. 400 megs. i want to find out how to shrink that down. probably i wont get around upgrading the ram though. unfortunately my holidays are over now and thus my work on that matter slows down a lot. will be back as soon as i have something to add here. As for the bottleneck: i checked the USB Pendrive to SSD transfer rates over and over again. It doesnt go much beyond 2 Mbit, most of the time it stays below that and the CPU is not working much. so i belive those SSDs which ship with the netbooks currently are really crap. They are too slow by any means. [EDIT] - with the latest release of Windows 7 (RC) i changed the mode of prepping my USB Bootstick. With a little free tool from Lexar called BootIt (some might know it) it is possible to convert a stick to a Local Hard Disk. This again makes it possible to format with NTFS. This, or changes in the new 7100 build sped up the install-speed to approx. 1,5 Hours i cannot say which one caused this dramatic increase compared to the approx. 5 hours before... - Driver Integration works well. - Unattended does not work. Information on this can be found in the vLite section here on these forums. [EDIT 2] - Installed latest build. Upgraded RAM before. Installation goes a little faster now. Not much though. - Noticed that no portable Office 2007 can be used. I tried Thinstall versions and other. Nothing works. All say they run out o Memory. This cannot be true though since there is always plenty left. Have not figured out the real reason. - Noticed that Skype 4 permanently uses about 70% of CPU on the Atom under Windows 7. This is bad.
  4. Hello all! I Have not been here for a long time because i gave up my hobby of toying around with windows XP. I found it too time consuming. Now i found something new and shiny and i want to play with it for a while. If you wish you can join in and help me make the perfect Windows 7 for Netbook install. I hope this thread might not become a bloated thread of people chatting away. I really hope this may be a thread which could serve as a decent reference for the future. I have little to offer yet. I have had a look around the Forum and i have found some very interesting things that can be used here. The one to start with is of course the whole story of booting a USB Drive and installing Win 7 from there. Hint: its the same procedure as with Vista. Nothing new here. I have a guide ready in German covering two slightly different approaches which i think are the most sleak and slick approaches. I will file a translated version here later. Second thing which is worth a note: Windows 7 responds to vLite very well already. There seem to be some bugs though. I have the impression that the calculation of expected size with removing components is somehow not right but it might also be me not understanding vLite system properly. I have so far done this: 1: got my stick bootable 2: vLited Windows 7 3: transfered source files to stick 4: installed what have i learned so far: to 1: making a stick bootable turns out to be really tricky because it seems to be a matter of compatibility between stick controller and Bios. On my netbook it was never an issue but on my pc it was horrific. to 2: removed as much as possible, ran into many installation errors, ended up with a disk that was reduced to somewhat like say 1.7 GB. Unfortunately removing more always led to some error. So what i took off was just basic things: Languages, Samples, Tablet PC input (Netbooks aint got no touch screen) and some little things like games, some very old drivers and such. no services - that always gave errors, no major components apart from Media Center (that caused no problem). Tweaks applied: only basic things like show opperating system files and hidden files. unattended never really worked out - have not checked why because i didnt find it interesting yet. to3: xCopy works a lot faster then the windows UI. No Secret. It is an integrated \system32\ tool in Vista, get its Params by typing xcopy /help at CMD. Am going to test Robocopy instead soon. Its expected to be even faster. Hint: get yourself a very fast USB Pendrive - saves you some Headaches. to 4: installing windows 7 on a netbook is no fun. really. it takes about 4 - 6 hours. don't laugh. its true. it gets through the initial stages very fast if you have a fast drive but then it just seems to get stuck when its processing all the information and setting everything up. that makes about 90% of the time. I guess thats because my netbook has a very slow SSD and also i believe that the serial-cpu, that Atom-crap, is slowing things down badly. it can only work orders serial, not paralell. which is a pain. but probably the slow SSD is the main bottleneck. am going to change that. but thats a different story. so what do i or we want now? I for sure want an Install that fits on a one GB Drive (will see if thats possible without crippling the system), an install thats opimized to run on limited hardware - so what about that freakin pagefile and hiberfile? they eat most of the space? and i want to know everything thats possible with windows 7 to reduce drive access. i will stay with SSD because that is the future so i will want to know and find out everything that makes windows leave that SSD alone as much as possible. Friends, let the work begin! [EDIT] Attached my Bootstick Guides (EN and DE). Hope you can do with the Translation attempt... Vista_Win7_from_USB_DE.doc Vista_Win7_from_USB_EN.doc
  5. Although there have been quite a few ways listed already now i wish to put in mine as well since i consider it fairly easy and it also helped with a peculiar situation you may encounter. HP already knows of a situation where you would format your pendrive with diskpart in vista and then try to boot from that drive. the bootprocess would then get stuck at post after the optical drives are accessed, right when the bios tries to access the pendrive. HP aknowledges this special situation only for two of their desktop-pc models and their own Pen Drives. However, i am running an AMD based system, which is realised on a gigabyte motherboard (GA-MA790GP-DS4H) which shows exactly the same behaviour. so all Diskpart-Methods would never work and i thought for a long time its my stick until i bought a new one. So i had to work out why. This i still have no answer too, but i found a method to get the pendrive to boot within this situation nonetheless. I found it by just fiddling around with things, by chance so to say. it basically is the method described by the topic-starter thegr8anand except completely replacing the Diskpart method with the aforementioned HP USB Mass Storage Format Tool. Its short and simple. AND it works on XP too. Do as follows: 1: create a bootable DOS Floppy (real or virtual if you have no floppy or download an image) 2: Start HP tool, select the Pendrive in question, select Quick Format, select Dos startup disk, point the tool at A:\ for the DOS Files or to the Folder where u have them downloaded to, then format 3: go to Pendrive, delete DOS System Files (u dont need them, they are just put in by the tool because it made a dos disk) 4: get bootsect.exe from your Win7 Disk, start it right from disk or put it in \system32 so u can use it from everywhere, goto CMD, launch bootsect.exe with the command /nt60 <DriveLetter>: (put in the letter of your pendrive), press enter, done. 5: copy over contents of the Win7 Disk to your pendrive 6: reboot, install (oh yes boot from the pendrive has to be set up in bios maybe, i forgot to mention THAT one lol) so why is it now that DiskPart creates a bootable USB Disk that won't boot on some machines but not on other? And why does the HP Tool create one that will? I want to know that tiny little difference. I want to know that really badly. So if someone understands that process and has an idea - please share your thoughts! Ressources: Diskpart reference by MS: http://technet.microsoft.com/de-de/library/cc766465.aspx Bootsect reference by MS: http://technet.microsoft.com/de-de/library/cc749177.aspx The HP Tool (also known as SP27213.exe or SP27608.exe): http://www.wintotal.de/Software/index.php?id=3181 What HP says about the problem, that some Pendrive/Bios combinations won't boot: http://h20000.www2.hp.com/bizsupport/TechS...=reg_R1002_USEN Everything thats necessary to get your Pendrive done as a bootable DOS Disk (you still need to fix the bootsector to be NT60 compatible afterwards with bootsect.exe!): http://www.bootdisk.com/pendrive.htm hope i could help a bit. sorry for the lengthy post. PS: i have written down a complete guide with both methods, currently available in german only, for those that are interested. Will translate it later on maybe. get it from the attachment if u please. Vista_Win7_from_USB_DE.pdf
  6. Well, dude, I cannot excactly help you as i'm not really a pro either, but just wanted to mention that i'm running a creative x-fi on an nForce 4 board, which recently happened to behave just very similar. After just another update from creative (they desperately try to get their x-fis back working under vista...) the soundcard just stopped working. It would still be visible in hardware manager but there would be no driver installed and an update of the driver would just return an error code 28 (timout while waiting for the installation to finish). After having messed around with different driver versions, cleaning the registry yet another time and deleting all creative files found on the system i finally managed tu F+++ up my Vista completely. Creative Support wasnt really supportive either as they where just wanting me to try the stuff i already tried plus doing this with a clean-boot state, which of course made no difference to a messed up driver installation. so i'm left with shifting around my data to manage a fresh vista install beside my current (too many things i cant quickly backup and transfer to my new vista) and then migrating important things from the broken install to the fresh... i believe you might end up just the same as vista still really badly suxx with these issues. one has to be prepared for this to happen more than this was the case with xp at the moment i believe.
  7. Oh well didnt expect an answer that soon. i actually remember the forums being quite slow. but on the other hand- havnt been here for quite a while. so thx bledd for pointing out a stupid thing i somehow never really noticed even though i'm rather sure i've read the darn license more than once. Of course i saw it at once when i checked back after getting your answer. as it is with people- sometimes we're having a blind spot just where we should have a closer look. thank god i'm not in a situation as desperate as the above mentioned... i just did it because its easy and comfy to prep a business sys with nLite. guess i'll have to do it the ordinary way in future then. cheers.
  8. bledd your comment throws up a question for me now. maybe if you come across this thread again you may want to answer this (or someone else who knows). why do you believe one should refrain from using nLite on Business Computers? is it because MS does not offer support for nLited systems? or is there a severe consequence in some way to be expected? please do not complain about this sort of question. I just figured i should maybe think about this issue since i haven't done this yet. I am actually using nLite on a business machine, well did use since its setup and working now ;-) thx for your time...
  9. Well, i'm only just reading myself into the whole thing. Really sounds like its gonna be a lot more easy right from the beginning, at least its prepared by MS already a lot more. Looks like the actual technology is a little more complicated (xml in the answer file, right?), but in the whole there's easier access all the way by means of specially designed assistants. Correct me if i'm wrong, but i believe its gonna be a massive big toy for all of us deployment and unattended guys... so i'm kinda looking forward to the first comprehensive guides. allthough i probably won't be able to contribute much myself since i'm gettin tied up in work more and more recently. But i enjoy reading your guys attempts and trials and trying a bit myself every now and again. Good luck to all you enthusiasts out there!
  10. Well, its not quite the same Topic, just very close: i had severe issues with the nVidia drivers on Vista RC1, so bad that i was unable to run vista on my machine actually. These issues were due to SCSI/RAID/S-ATA Problems. After having configured the HDD's in a way that Vista would recognize them at all with those nVidia drivers it then still rejected the driver after installation at first boot due to a missing Certification by MS. Well, that was a few Weeks back and i havent tested again yet (was too frustrated). Sorry for drifting slightly Off_Topic,just felt like expressing my frustration with these darn nForce Boards and Vista... Not nice, really... sneaky
  11. Sneakyghost

    nLite 1.0.1 Final

    Sesshoumaru did you check wether you disabled HID Input Service anywhere (pre/post install)? without that service special keys wont work. According to your "last session.ini" you set hidserv to 4, i guess "hidserv" is "HID Input Service" and option 4 is uhmmmm... probably disabled or something like manual start?? sorry am not a professional with nLite logs....
  12. Well i might be entirely wrong here, so take my apologies if i am.... with my nero7 experiments i came to the conclusion that none of the usual "quiet" msi-switches work but one, which is: "/passive" i think this, because my (german) nero.msi did not react to any of the quiet switches in the usual manner, it only did a silent job on the "passive" switch. of course i might just have applied the switches in the wrong manner, but maybe it is just so that nero msi only takes passive... hope i was helpfull here, even though its an old thread... sneaky
  13. Once Again: big thx @ allanoll for keeping up with those guys at nullsoft! just in time for me to still add it to my nearly finished UA. won't do much on that one for awhile so i'm pretty happy that this one still came in b4 i'm finished... great job man!
  14. maybe i've missed somethin the past few month but I'm pretty sure that it's still not possible to install the current versions of the free antivir silently. this function has been removed by H+B EDV way back in winter 2004. its now only available for sys admins who work with the expensive corp edition or other non-free versions. if that is not so i will apreciate a short note on that here since i'm looking for ways to get that function back myself. my solution is to keep using the old (last version with silent switches) and update manually after install finishes. greetz sneakyghost ps: b4 i forget that: even with that version u have 2 use the setup.inf method! doesn'work otherwise...
  15. hi allanoll! havent been here for ages... after i finished my ua which worked fantastically well thx 2 u guys,i never came back. now its time for updating a few things. i wonder what happened 2 the new .msi? will u still do that? or is there a new thread mayb? hope u know how much people like me apreciate ur work! thx. sneakyghost EDIT: sry been blind. search didn't turn up 5.09 the first time. found it now. big thanx.
  • Create New...