Jump to content
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. ×


  • Posts

  • Joined

  • Last visited

  • Donations


Posts posted by pSycho-Y2K

  1. It works in Windows XP as in Windows 7, but with the forced restart at the end :(

    I'm trying to figure out what caused this and I was curious if someone else experienced this also.

    Could it be that Windows 7 has elements which needs to be installed on XP during installation which will force a reboot?

    I'm using the exact same version of my .msp file in Windows 7 as in Windows X.

  2. Hello everybody, I've used the Office Customization Tool to make an unattended Office 2010 installation. This all works silent (Basic display level with Suppress Modal checked), but unfortunately after the installation on a Windows XP client, it reboots. On a Windows 7 machine this doesn't occur. What's up with that? I'm using the silent installation during RunOnceEx and it spontaneously reboots after installation. Can it be suppressed for Windows XP? :)

  3. I tried reproducing your problems and I couldn't. I downloaded like 15 driver packs and db created clearly without problems. Would it be possible that you (psycho or xecutor) to create me some 7zip file of your drivers db and put somewhere to download (can be big) or maybe try to isolate a problem to specific driver, amount of drivers?

    Edit: I found the problem, it's in one of external libs i use. Will try to fix, ask to get it fixed.

    I use all drivers for Windows XP from DriverPacks.net. I download all de 7zips and extract them all in a single folder called Drivers which is located of the root of my USB-Harddrive (Z:\Drivers).

    P.S. Any progress on this MadBoy? :)

  4. Hello psycho. This bug seems to be related to database prepare. I'll take a look at code later on but can you check if it crashes only on that one netbook? It shouldn't be related to hardware because what it is doing then is going thru all drivers and putting them in database. So if it crashes on one notebook it should crash on the other if you're using same share/folder which happens to store the drivers.

    Hello MadBoy :)

    It's not netbook related, it also crashes in VMware Workstation which never happend with your older releases, check the screenshot.

    I'm going to try your previous version.

    UPDATE: It seems only version is affected, perhaps your new driver database creation is the problem?


  5. Hey MadBoy :) I haven't seen you for a while on the forum. Did you had time to do some progress on your next release in the past two months?

    Unfortunately I've come across a nasty bug which I like to inform you about. I ran the tool on an Acer Aspire One netbook, so I don't know if the problem is related to its devices. Perhaps you can debug what the problem is? Also, I'd like to know if the tool is (or could be made) Windows 7 compatible :)




  6. Great job for fixing the problem! :thumbup

    But, while this problem is solved, another one just pops up :blink:

    The hardware-window buttons doesn't get pressed anymore, see the attached screenshot.

    MadBoy, forgot my problem? It is still unsolved in your latest release. :(

    I attached the XML and logfile. See the screenshot which I posted earlier, which is basically the same.



  7. Great job for fixing the problem! :thumbup

    But, while this problem is solved, another one just pops up :blink:

    The hardware-window buttons doesn't get pressed anymore, see the attached screenshot.

    As requested: my current driver folder (which resides on a USB HDD which I always use for fresh installations) contains the following from DriverPacks.net (mostly 3rd party and beta):



























  8. I have exactly the same problem as pipster :} Let me first give you guys the details:

    - USB Flash Drive: Kingston DataTraveler 2.0 8GB

    - Partition size: 8GB

    - Filesystem: FAT32

    I used the following guide by aviv00 (Post #1):

    Guide - Install WinXP From HDD or USB Drive Or CD, 1.3 Final [2 Methods]

    But, there was no migrate.inf involved.

    I used MkMigratgeInf_b.cmd posted earlier in this thread and created a migrate.inf and moved it to $WIN_NT$.~BT

    The output was unfortunately D: :}

    Then, I used MkMigrateInf2.cmd from USB_MultiBoot_10 and created a migrate.inf and also moved it to $WIN_NT$.~BT

    The output was also D: :}

    As a last resort, I cleaned the USB device drivers with DriveCleanup, re-attached the USB Flash Drive, and tried the solution by piper copying the value of \DosDevice\G: into the migrate.inf (In my case it was G:), but it also didn't help :(

    Then, I was thinking:

    - Is migrate.inf called during the txt-setup with the guide by aviv00?

    - Or is this only getting parsed with the USB_MultiBoot_10 solution? (since this is using a different approach installing XP)

    I hope you guys can assist me like you did with pipster :)

  9. Here already such dd example in Chinese: http://bbs.znpc.net/viewthread.php?tid=550...t=dd&page=4

    The 60th topic.

    I translate here

    dd is a strong command, personally I think this is anoter most powerfull command after map command of grub4dos.

    By using the switch of "bs, skip, seek" we can copy file to file, sector to sector and the byte to byte of file, any position can be wittern (wether the file is read only or have NTFS right, Added by victor888).


    1. for a complete write, the byte of target file must be more than or equal to source file.

    2. The target file should be in device, no matter what the file content is.


    This is a dos batch on (fd0) name path.bat:

    set string=abcdefghijklmnopqrstuvwxyz

    set path=¥:

    goto main





    goto end



    The first line is 37 bytes (in fact, there ENTER or SHIFTLINE charactor bytes at the end of line, for the sake of demonstrating the use of dd command, the bytes are omitted.)

    The second line is 11 bytes.

    Then we could write any charactor to the second line.

    e.x replacy ¥ in the second line to certain letter, juse do the following:

    dd if=(fd0)/path.bat of=(fd0)/path.bat bs=1 skip=11 count=1 seek=46

    hence, the second line was replace to set path=a:

    (bs=1 means one byte as read unite,count=1 means only write one block defined by bs switch, here is one byte. skip=11 means skip 11 bytes including space. seek=46 means skip 46 bytes when write, that is write the 47 byte ¥)

    Certainly, we can do booting disk this way:

    dd if=/pe.img of=(fd0) or

    dd if=(cd0) of=/cd.iso

    Writing boot sector to imge fiel is also convenient:

    dd if=(hd0,0)+1 of=/dos.img

    We can study above to chang boot.ini without dificculty.

    Is there any progress on this yet? I tried your dd command approach to change the rdisk value in boot.ini, but it gives me a fatal error screaming something about "Cannot write resident/small file! Enlarge it to 2KB and try again" :(

    I just know you guys are on to something as I can fully understand the problem here and also searching for alternatives and manipulating the boot process for the GUI mode to start correctly without editing the boot.ini manually.

    Just a quick test where I got the error:

    title Windows XP SP3 - Phase 2
    root (hd1,0)
    dd if=(hd1,0)/boot.ini of=(hd1,0)/boot.ini bs=1 skip=22 count=1 seek=69
    chainloader (hd1,0)+1

  10. Hello pSycho,

    All you need is in the code already. All you have to do is pass the name to program right (a.k.a with & in front of the letter that is underlined). Like

    N&ext if e is underlined or without & but then you have to pass ext

    &Next if N is underlined or without & but then you have to pass Next

    Ne&xt if x is underlined or without & but then you have to pass xt

    Hope you understand what I'm saying :)

    With regards,


    Only new features are not implemented but this one should work fine if correctly used.

    Fantastic my problems are solved! :thumbup It works like a charm. Tumbs up for your help! Can't wait to see more features in the next update.

  11. Sorry for the late response, I was very busy in the past weeks.

    But, I think I have success with your latest pro-s_test.exe :D The following windows appear when the script is run:

    pro-s_test.exe "Wizard Hardware toevoegen" "lgende" Annuleren



    Found New Hardware scans for devices...




    Found New Hardware terminated...

    1 STOP

    Found New Hardware starts again and scans and stops at the question if the hardware is connected

    So, what can you say about these results, is the problem now resolved? :) And could this fix be in your next release?

  12. What if you type in

    script.exe "Wizard Hardware toevoegen" "Volgende >" Annuleren

    script.exe "Wizard Hardware toevoegen" "&Volgende" Annuleren

    I ran both commands, but the outcome is like the screenshots I posted earlier. It seems that "Volgende", "Volgende >" and "&Volgende" doesn't work. What could it be, it looks like the button isn't recognized? Very strange :blink:

  • Create New...