jjn1056

Member
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jjn1056

  1. The HPT370 is actually a PCI card that plugs into the motherboard. It was called a "RocketRaid 100" and it's a couple of years old. I used it to control two mirrored backup drives on my development system, but now it's on my girlfriend's computer, after I decided to spend the money on some real backup for my development server. So I have some extra piece of mind that she is on a mirrored RAID setup and gets some extra data protection. I attached the latest drivers that I got from the Highpoint website. These drivers definitely work if I install then manually. I'll run the hwid program on her PC a bit later and send that along as well. Let me know if you come up with anything. Right now my girlfriend is using that machine so unfortunately I can't do any testing for you, but next time I need to rebuild her desktop I'll give the driverpacks a try again. I hope to see this project really grow because I can see that is can help a lot of people. However I don't know enough about windows hardware setup to meaningfully contribute code Good luck rocket_raid.zip
  2. Final upate. Even thought I got my installation running using the hacked up txtsetup.sif file there was quite a bit of trouble once windows xp was running. Since I don't have any more time to devote to this issue I am just going to go back to my old way of creating these unattended disks (XPCREATE with seperate profiles for each of my friends). Maybe in 6 more months this will be mature enough for someone at my level to use. The driverpacks are a really great idea but unfortunately as someone running my own full time business I can't devote any more effort to tracking down these issues. I hope the log of my journey trying to get this interesting project running turns out to be really valuable to someone else down the road. Good luck to you all, peace out.
  3. Okay, there is definitely something wrong with the txtsetup.sif file. I replaced the one created by the driverpacks with the working one created by xpcreate and the machine installed normally. So that means that there is something in the txtsetup.sif file that is causing this trouble. I'm attaching the working txtsetup.sif file for reference purposes. It's about 80% of the size of the one created by driverpacks. I am guessing the trouble is that something else in the txtsetup.sif file is taking the place of the 'real' driver or causing my system to miss it or something. It's probably some of those other semi matching hardware ids, but unfortunately when I editted the existing txtsetup.sif file to remove that stuff I got a installation error that said the txtsetup.sif file was invalid. So I am going to let this install finish and then see if all the other hardware was correctly detected. If so then I will troubleshoot this issue some more. Any gigabyte motherboard owners out there with any comments? Gosh, you guys/women are an awefully quiet bunch I'll just keep adding items to this group on the hope that it helps someone else in my shoes someday.
  4. Okay, I tried commenting out the matching items but I still got a BSOD at first reboot. My girlfriend is starting to get mad at me for working on this all weekend. I'm not sure what to try next, but I will keep trying to figure out what is the difference between the working on non working disk. One thing I noticed is that all the driver files in the /D/... folders are compressed. I guess this isn't the issue, but it is a difference. If anyone who knows about this could give me some comments I would appreciate it.
  5. Alright I was pretty stupid. Seems I diffed the wrong txtsetup.sif file The txtsetup.sif file from the XPCREATE disk that works only has a single match for PCI\VEN_1103&DEV_0004 which is my hpt370 but on the txtsetup.sif file created by driverpacks I get a bunch of matches: PCI\VEN_1103&DEV_0004&REV_01 = "hpt366" PCI\VEN_1103&DEV_0004 = "hpt3xx" PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_04 = "hpt3xx" PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_03 = "hpt3xx" PCI\VEN_1103&DEV_0004&SUBSYS_00011103 = "hpt3xx" PCI\VEN_1103&DEV_0004&REV_03 = "ahpt3xx" Now I am not an expert on how this works. In the working XPCREATE disk I only have PCI\VEN_1103&DEV_0004 and that works correctly. In the driverpacks I have both PCI\VEN_1103&DEV_0004 PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_04 the second of which is a closer match to what is inside of hwids.txt file. I am wondering if all this similar things are causing me trouble. If there is someone out there with more knowledge of this I would appreciate some feedback. I am going to try commenting out all the entry that are not hpt3xx and see if that helps.
  6. Additional testing. I can see that the relevent section in the hwid.txt file is: PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_04\4&3191A3E6&0&5070: HPT370 UDMA/ATA100 RAID Controller I can see an entry for "PCI\VEN_1103&DEV_0004" in the txtsetup.sif file for both the disk created with driverpacks (which BSODs at first reboot) and the XPCREATE disk (which installs cleanly). I figure this is the relevant section. I was not surprised to find it in both files, since the diff I did on the said they were identical. If anyone know if I am looking at the right stuff, please let me know. Now I checked the /I386 directory for both disks and I found a file called "hpt3xx.sy_" in both that are clearly identical. So this is starting to make me think something is either wrong in my winnt.txt file or that something is being loaded that is incompatible. The motherboard has integrated SATA controllers, btw. Seems some other people are having trouble with Gigabyte motherboards, but I am not seeing if there is any resolution. Anyone with a gigabyte motherboard that had this trouble, even with a different PCI IDE controller, manage to solve it? Thanks! Here's my current winnt.sif file, don't know if it helps. WINNT.SIF
  7. Some updates to the issue. Today I got a clean windowsXP installation with only SP2 + ryans updates intergrated. This is my baseline unattended DVD that sets up windows and all the updates for me and I know it works. I then integrated the drvierpacks and build a selfbooting disk. Unfortunately I got the same problem as yesterday, so this issue is not because of using XPCREATE yesterday. The disk I created will actually work against a computer that is not trying to boot off the raid array, so I know it's a good disk. Funny, but when I take the very same clean disk and integrate the HPT370 driver using XPCREATE I get a working system. So I am trying now to figure out what XPCREATE is doing differently. I did a diff against the txtsetup.sif file from the driverpacks disk and the XPCREATE disk but they are identical. So I will look further into it. Any suggestions about what to check would be appreciated. thanks! BTW, in txtsetup.sif, there is a htp3xx.sys and a rhtp3xx.sys file. Does anyone know the difference? Am I looking at the right thing for the highpoint rocketraid100 IDE controller? Never mind, I can see the htp3xx entry is the thing I want.
  8. I'm getting that BSOD issue at the first reboot during my unattended install. I am guessing that my IDE controller driver isn't being installed. Here are some details and I have uploaded a HWID text file I made using that tool. Any suggestions would help me a lot. I searched around a lot but can't seem to fix this. Motherboard Gigabyte GA k8nsc-939 Booting off a Highpoint RocketRaid100, which uses the htp370 chipset. I am building my attended install with XPCREATE, but I don't see how that would matter much. I've been building unattended installs for more than a year and am hoping to make this work so that I don't have to have 10 different setups for each of my friends Thanks for any help or suggestions. hwids.txt
  9. Hey, I don't have a specific answer about installing all the hotfixes from a batch file, but I'd like to encourage you to take a look at that recovery CD and see if you could copy and customize it. It's probably just a normal windows install with a $OEM$ directory for the stuff toshiba added. You could probable add stuff right in their. Most of the hotfixes I slipstream right into the windows installation using the /intergrate option of the hotfix (for the newer ones that support it) You can check out unattended.msfn.org for some help on how to put all the updates into the windows cd you create. It's actually not so hard. I found it was worth the time to read those documents and cruise the forums for help and advice. The people who stop by here are very cool and help out a lot. I'm guessing you could build a batch file of the hotfixes and install them all at once using the /quiet option, but you might have trouble with the order of the hotfixes. Some only work after others have been put in place. good luck!
  10. Is anyone mirroring this app? I just get "Bandwidth exceeded" when I try the links from the first post of page one? It looks cool, I'd like to try it
  11. Well, If anyone else does a search on this problem and finds this forum, it appears that runonceex is only for the HKLM key, not the KHCU key. If I ever find out otherwise, I'll update this thread. thanks!
  12. I actually run all my application installations from a series of batch files that get executed when the Administrator auto logs in the first time. I find that many applications need a 'real' user and can't be installed from cmdlines.txt. I figure a lot of other people must do the same, since the HKLM RunOnceEx method is popular and is described on the homepage. The problem I have is that after I create the users for the machine, which is the last thing I do under the administrator account. I need to make sure that some stuff runs the first time a user logs in. This has to happen for each of the users I put onto the system. This is running user specific stuff, like deploying a firefox profile and installing open office from a local administrative install point. I can't user the RunOnceEx under HKLM because this will run the next time anyone logs in. I need something to run each time a user logs in the first time on the machine. I can do this with the runonce under HKCU, but I find that because it doesn't give such nice visual feedback and because the desktop finishes loading before all the stuff in runonce finishes, it's a bit messy and could cause some confusion to my users. So I would prefer a nice clean and visual feedback to the finalization of a user the first time she logs on. That's why I asked if anyone knows if there was a RunOnceEx for the HKCU registry setting. Someone posted an example of what this could look like but it doesn't work for me. So the question I am trying to answer is if the above registry example SHOULD work for me. I'm hoping someone out there has time and is curious like me to get the answer. MS knowledge base does speak of a RunOnceEx registry key under HKCU but there are not working examples on the MS site that I can find. Thanks for all the suggestions so far. This website and all of you in the forums has made my life much easier over the past year as I learn about windows deployment. --john
  13. Hmmm, see I tried that exactly and nothing happens. After I restart and log in I can open the registry and I see all the keys are there, just like above, but nothing happened. Is this supposed to work? Any other WinXP SP2 users out there have time to give the above a try and let me know what happens? At this point it's starting to become a mania for me. I know I could just as easily code up something myself but I'm curious. Maybe I messed something up when I was installing my box. I have no idea. Thanks for the help so far!
  14. Okay, For global post installation I use: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx to install system wide apps and settings. That all works just the way I like it (thanks to the guidence of this website ) However I have a few applications the need to run something once when the user first logs in. For example, if you have a multiuser machine with Open Office, each user on the machine does an install from a local administrative setup. The same things goes with Firefox and ffdeploy; you have to run something to copy the profile info into the new user. Now what I am doing is adding a bunch of registry keys to the default user (I have to load the NTUSER.dat hive first) so that when I make new users they inherit those keys. So far so good. But... I can do: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce] "1"="C:\\Program Files\\Mozilla Firefox\\createprofile.vbs" and it works but I don't get the nice RunOnceEx dialog. Also I find that my desktop loads up before all the stuff I have in RunOnce finishes, so I get this wierd problem where not all my applications are installed until a minute or so after the desktop loads up the first time. I'd like to do [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnceEx] "1"="C:\\Program Files\\Mozilla Firefox\\createprofile.vbs" so that it pauses loading the desktop and gives some visual feedback as to what is happening during the first time you log in. But this doesn't seem to work. Is there such a thing as RunOnceEx for the current user? I've searched all over this forum and the microsoft knowledge base and google and I don't get a straight answer. I've found examples at MS for this but none of them work. So either XP doesn't support this or I am doing something really wrong. The main reason why I want to set things up this way is that I like to put all the installation stuff for an application in one place. That makes it easier to maintain. Otherwise I have to run the installers during the time I create users, which to me seems a bit messy. I know in the end it's all the same, but like a lot of you I tend to be a perfectionist, otherwise why would I spend so many hours creating my unattended install? So if anyone knows a way to solve my problem I would appreciate it. I figure I can't be the only one to try something like this. Thanks! John
  15. Astalavista, Thanks for the direct link, it really helped me out! jjn