BogdanV

Thanks for your reply, although if I'm not mistaken, in Windows 2000, if you shutdown the system via Progman, the BIOS wouldn't turn the power off, instead the PC would halt in 256 colors, 640x480 with a message box stating that "it is safe to turn off your computer now", so probably the OS closed most essential parts of it. But then again, I don't think you could trigger the boot manager or anything similar without coding a trigger within the kernel, even though the system would turn itself off without cutting power to the PC, so its back to your post.

The description sums it up. Mainly that's what I love about Win9x. You could terminate the Windows session, fall back to DOS and restart the Windows session without wasting time going through POST. I know that NT doesn't use DOS to boot, but, speaking of this, is it possible to fall back to the NT boot manager and start XP from it again ?

Thanks for your replies. I'll see what I can do. As for XP's HAL and ntoskrnl, I was afraid that something like this might get caught in the middle, but I'll see*. Well, as far as I'm aware, this driver, albeit useful, is just a primitive solution as it doesn't offer any hardware acceleration. Its basically a adaptation of XP's standard video driver, for 9x OSes. *that is, after I fix drive C (where 98 resides) because XP trashed it.

Being annoyed by the fact that there's no 9x driver for X1300 and the fact that it'll take probably more than a year before I replace my video card with one that does have working 9x drivers, I thought on venturing on my own, trying to adapt a 2k/xp driver to work with 98SE. I am aware that NT is a completely different story from 9X, but nonetheless, I thought on seeing what can be done as I've heard that 98SE happens to have WDM support as with 2K and XP. Anyway, I've trimmed the INF containing all the necessary data, leaving just the parts relevant to my video card, changed all the reg keys that pointed to (local machine) "Software\Microsoft\Windows NT\..." to the probably equivalent entry, "...Microsoft\Windows\..." and also changed the version signature to "$Windows 95$" (or should I have used $Chicago$ instead ? ). After doing all of this, I tried updating the display adapter with the INF I modified, but I ended up with a message stating that the file contains no information about my hardware. Once I've seen this, I made a separate INF, to register all the keys that needed to be added, and manually copied the dll files in their respective folders, according to the INF file. I rebooted and nothing changed (something I was kind of expecting). In the end, can someone please tell me what is the system expecting to find in the INF file so that it would "contain data about my hardware" ? Thanks in advance!

After some search on the net, it seems that for me, the cheapest way to get an Xbox Arcade is by ordering it from the US (as it seems that its sold there for ~200$). I've checked the links provided by Microsoft's site, but the stores listed don't seem to offer shipments outside the US. This being the situation, I thought on asking here if anyone knows of any US store that does offer shipments worldwide (more specifically, to the EU, Romania). Also, ebay is out of the question in my case, so, except that, any suggestion is welcomed! Thanks in advance.

Okay. I compiled another CD without touching anything from the fdv files. After launching the setup from WINNT32.EXE (didn't burn a CD) and rebooting, I end up with a "uniata.sys not found" setup error. Rebooted and checked "$WIN_NT$.~LS". To my surprise, Setup didn't copy uniata, although I have included the file both in FDV and in Source, Source/I386, in .sys and .sy_ forms. Once I've seen that, I copied the file in $WIN_NT$.~LS's I386 folder. It found uniata and carried on. But..., when copying files, it started throwing quite a lot of "file not found, retry/ignore/skip" messages, all ranging from NT4ICONS.DLL to mrukill.sys and usbintel.sys (12 in total). It passed over this and entered the graphical stage of Setup. There, it started with SPCHAPI.INF not found and carried on in the hardware detection part with some files that I wasn't able to track in my HFSLIP folder and not even on my Win2k CD. (They are: usbui.dll, swenum.sys and mga.sys) Also in the detection part, it warned me that Setup was unable to initialize several network related installs. Then, it carried on with the Regional Settings. After that, in the final phaze, it threw a file not found error regarding "desktop.scf" and after several seconds, it rebooted by itself! All these happend with the following setup of my HFSLIP folder: -Win2k SP4 I386, CDROM_IP.5, CDROM_NT.5, CDROM_SP4.TST ->SOURCE -latest FDV files (downloaded from the forums) -> unpacked in FDVFILES -uniata.sys + uniata.sy_ (renamed) ->HFSLIP/SOURCE and FDVFILES As a note. uniata.sys was taken from ReactOS 0.3.8

Sorry to reply after such a long time, but yes, I never had any problems running Win2k and XP on my machine. It always worked since I never had any clue about atapi and uniata until this thing hit me (oh and both installs were clean installs). Hmm.., well, I do remember at one point in the tutorial mentioned in my first post I had to do the following: . That's the only modification I've done to TXTSETUP.

About getting into Safe Mode, for me, keeping CTRL pressed before boot, brings up the boot menu (F8 worked for me on 2k and xp, don't know about win98). As for DirectX, well, the 6.0 version is the one that comes with the installation of win98. I would've said that your dx-related issue would have came from a faulty/scratched CD, but since you said that scanreg fixed it, it seems that the issue's not from the CD. Also, about Ace FTP, are you shure it didn't come bundled with any software you installed or as a install option within another program you might've installed ? Anyway, since you mentioned scanreg, indeed, it seems that the problem was strictly registry-related. Probably the New Hardware Found Wizard, coupled with dx6.0 and "aulosetp" (seems to be some kind of setup service, judging by the name) came from a corrupted registry that involved both dx6.0 and whatever driver that is linked to "aulosetp". Probably the corruption came from the driver's registry entries. Oh and since it involved dx6.0, its certainly a multimedia related device (audio, video). Probably this ace FTP program messed up the driver's registry and by doing so, it affected dx's registry too. At least this is my oppinion. I can't tell for sure how possible/plausible my idea is, but this is how I see it.

Generally, I get my info from the comments left out within such files. Unfortunatly, there are numbers that aren't covered. I tried google-ing for such information but I wasn't able to find much. Oh and why do I need this info ? Well, I'm trying to modify my ATi X1300's driver to make it work in Win98. I seem to understand the structure of these files and I'm able to learn on-the-fly, but for certainty's sake, I'd really like to know where I can find a list of all the numbers used to designate Windows's folders (ie. INF folder = 17). Also, since this is the first time I'm trying to change a driver, are there any resources/advices that I should take into consideration before starting this project ? Also, would there be any commands that the driver would try to execute that wouldn't be compatible with win98's kernel (and thus would cancel my efforts) ? Thank you for your time and thanks in advance!

Thanks for your reply! I got and applied several of the fixes that seemed related to network/communications, but my problem persisted. I also tried pinging my ISP according to its DNS server address. I got a reply, which is good. Anyway, after several good hours of head-bashing, it seems that my problem is infact ISP-related. I'll be calling them Monday and see exactly what's the problem. (it seems that there are discrepancies between what I've got and the type of service specified in the contract). All in all, thanks everybody for your kind help!

Thanks for your reply! I'll be sure to check. Also, are there any settings that I can "print-screen" that could further help in solving this problem ?

Well, does anyone know anything regarding this issue or are there any parts of my post that aren't understandable ? Any reply is welcomed.

More exactly, I'm using RASPPPOE in order to connect to my ISP. For several years, I've had no problem in connecting to the internet (with win98), but now, after deciding to go back to win98, I've ended up with a weird issue. Basically, I'm able to create my connection and login with my ISP, but when I open Firefox I end up with a blank page after some time. (IE throws out 404 after trying for some time). For those who are from Romania and their ISP is RDS, well, usually I receive their default "how-to-connect" page (with no instructions for 9X), but now, regardless of how I set the IP (auto/manual on both TCP/IP entries), I only get a blank page or a 404 after some time. Also. the connection is OK since I'm using the same PC on dual-boot with Linux to write this message. If anyone has any idea on how to solve this, please tell me. Thanks in advance!

As the title suggests, I'm having a hard time trying to make my "HFSLIP-ed" install to work. As a introductory note, I've followed Vorck's "Windows 2000 total slipstream" tutorial: http://www.vorck.com/windows/2ksp5.html, applied of course on a win2k setup. My problem, as far as I've managed to track it, is the fact that the uniata driver fails to work on my PC (fact indicated by the "INACCESSIBLE_BOOT_DEVICE" stop message that "greeted" me immediately after install and the fact that on Virtual PC, it worked flawlessly, which lead me to believe that the problem is driver-related). Since the default atapi driver works on my PC without any noticeable limitations on my SATA drive, I tried several methods of replacing uniata with atapi. Sadly, all failed. What I tried: 1.Commented-out all entries relating to uniata in txtsetup.sif and layout.ini (as mentioned on Vorck's site). Result: either a "uniata.sys not found" halt error, or a setup that continuously popped-out false "file missing" reports during copy, coupled with a snail-ish install that never finished. 2.Tried renaming atapi.sys to uniata,sys, but setup's file protection "caught" me ("uniata.sys not found" halt error). 3.Compiled without deleting the "[uniata]" header in txtsetup.sif. It didn't work (can't remember exact behaviour though). 4.Installed in parallel a unmodified version of Win2k and tried changing the registry entries as per this site: http://www.mostlycreativeworkshop.com/Article11.html (it details on how to move a IDE drive to another PC, without throwing the "inaccessible_boot_device" stop message). This last step worked half-way. It passed the "Windows loading" start-up screen and did a auto-reboot right after popping the cursor on a black background. This is as far as I've managed to go. If anyone could lend me a helping hand in solving this issue, I'd be more than grateful !