NINA TAKES A LOVER A film review by Steve Rhodes Copyright 1995 Steve Rhodes
RATING (0 TO ****): * 1/2
NINA TAKES A LOVER tells the story of a journalist (Michael O'Keefe) who is interviewing people about love and infidelity in the 90s. Among the people he interviews is the central character of the show, Nina (Laura San Giacomo), her friend (Cristi Conaway), and Nina's lover, a photographer (Paul Rhys). They each tell the stories of their affairs to the journalist while sipping espresso in a quaint coffee shop in what appears to be San Francisco.
Nina's friend's lover (Fisher Stevens) is a guy with a scruffy beard who makes perfect espresso at another coffee place. This is definitely a 90s movie. We have heavy drinking in half of the scenes, and it is all great coffee. The 50s movies featured beer drinking regular guys. The 60s flicks were filled with young people doing drugs. In the 70s we had cocktails and certainly in the 80s we saw lots of wine, especially white wine as the beverage of choice. I guess with the 90s here, rather than having characters being plastered and passing out, we will have them wired and hyperactive. But I digress.
NINA TAKES A LOVER is a movie where not much happens and the tone of it all is highly subdued which is reflected in the dreamy music. Overall, this can be a very soporific movie so don't go to the 9:30 showing. I would expect that the reaction of most people seeing this movie will range from mild boredom to a mild rapport with the characters. It is not a movie that is easy to get excited about or to dislike.
Laura San Giacomo who was so wonderful, as was everyone else, in SEX, LIES, AND VIDEOTAPE, plays a fairly reserved lover in this movie. Her husband goes out of town for three weeks so she get bored and looks to find a lover. Her married friend is ahead of her and already has hers. Spouses are not visible or talked about much--romance is.
The script and the directing were done by Alan Jacobs who needed to put more oomph in both. I like the characters he created, but I kept hoping in vain for them to come alive. Jacobs seemed interested in creating a mood piece with a message. He succeeded in the former although I wish he had more ambitious goals, and he failed in the latter.
The cinematography by Phil Parmet was a little unusual. In order to emphasis the separateness of people in a relationship he was constantly filling the frame with one person and then panning over to the other. It was a technique I could have done without.
The script makes an attempt at a big switch towards the end of the movie. I did not like nor buy this part at all. It felt as if they had gotten bad scores when test marketing the show, and they tacked on the changes as an attempt to make the movie more involving and to wake up the audience.
The movie is too long at 1:40. It is rated R for numerous sexual scenes and scenes of partial undress albeit, with one possible exception, there is no nudity. The movie would be fine for older teenagers. On the other hand, I do not recommend it to anyone, and I award it * 1/2.
**** = One of the top few films of this or any year. A must see film. *** = Excellent show. Look for it. ** = Average movie. Kind of enjoyable. * = Poor show.  Totally unbearable.
REVIEWED WRITTEN ON: March 30, 1995
Opinions expressed are solely mine & not meant to reflect my employer's.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Software Engineer with thorough hands-on experience in product development. Supportive and enthusiastic team player dedicated to streamlining processes.
1.Enhancements done on existing Sales platform with new features like SMS manager, UI optimizations done with upgraded versions and making the application more compatible and responsive.
2. Worked On Metromeets onboarding flow using Ant designs, React, Typescript.
1.Enhancements done on existing CRM with new features like Multifacility, UI optimizations done with upgraded libraries and making the application more compatible and responsive.
2. Lead the development of Warehouse productivity tool by coordinating with both BE and FE.
3. Taken the responsibility of growing 4 junior developers
4. As a tech stack I have worked on React, Redux, Angular(1.x), HTML5, CSS3, Styled-components, Redux-form
1. Key responsibility is on to building the eCommerce flow at Agrostar. This has real time dashboards, eCommerce workflows, Order management and processes.
2. Implemented crop lifecycle management workflow for the farmers on top of the agronomy prescribed schedules and practices. Automatic calls/Tasks triggering mechanism on the agents dashboard for increasing agents productivity
3. Farming data capture mechanism for giving farmers the best recommendation possible.
4. Worked on Progressive web app which is another source of placing orders for farmer, is build in React
A cloud based smart telephony solution that comprises of Smart routing, Voice bots.
Key responsibility on building dashboard for Routing, Auto SMS, Call logs. Developed the various responsive pages and its architecture in accordance with to UI specs.
Technology: HTML5, CSS3, Typescript, React, Redux, Ant-desigs, Styled components
Key responsibility on building CRM tool (Customer-relationship management) is a web application which has an approach to manage a company’s interaction with customers.
This platform provides the features like farmer profile creation, Order placement (e-commerce flow) & report generation which helps to maintain customer history.
And this web application is used by Sales Team(CSR), Operation team, Procurement team.
To be able to make quick delivery for the farmer, we have introduced the concept of multi-facility. It is developed for fast delivery of products to farmers reducing the lead time.
Technology: HTML5, CSS3, Javascript, Angular(1.4), ng-react, Bootstarp, underscore, React, Gulp
Designed and Built frontend for an Agronomy knowledge based Crop schedule management tool.
The platform is built to provide intelligent notifications, based on sowing date, manual-input based weather advisory information, disease solution recommendation
Build our own grid system and all components as a packages.
Technology: HTML5, CSS3, Javascript, React, Redux, styled-components, Redux-form, Redux-thunk, React-router
Designed and build frontend application for warehouse productivity measuring tool.
This application is basically to track the warehouse productivity like Inbound, Outbound, Return, Miscelleneous task, etc.
Designed UI component and UI flow for Inbound, Outbound, Return, Miscelleneous.
Technology: HTML5, CSS3, Javascript, React, Redux, styled-components, Redux-form, Redux-thunk, React-router
Agrostar Lite is a PWA(Progressive web app) app is used for field officers to place orders from the field for new and old farmers. It is integrated with CRM which maintains the order history of farmers through different sources.
Technology: HTML5, CSS3, Javascript, React, Redux, styled-components, Redux-form, Redux-thunk, React-router
GPA: 4.5
Percentage: 59%


Citizenship Amendment Bill: How Amit Shah Defended Excluding Muslims
The Lok Sabha voted in favour of the introduction of the bill after protests by opposition leaders.
by Akshita JainRuckus, ruckus, ruckus.
As Union Minister Amit Shah introduced the Citizenship (Amendment) Bill, 2019 in the Parliament, Opposition parties were immediately up in arms and asked the government to withdraw the bill.
Parties, including Congress and BSP, had said they will oppose the bill “tooth and nail” because it is against the Constitution and its secular ethos.
According to the proposed legislation, members of Hindu, Sikh, Buddhist, Jain, Parsi and Christian communities, who have come from Pakistan, Bangladesh and Afghanistan, and facing religious persecution there will not be treated as illegal immigrants but given Indian citizenship.
Introducing the bill, Shah said, “This bill is not even .001% against minorities in the country.”
The Lok Sabha voted in favour of the introduction.
What Amit Shah said
The Home Minister said that the bill is not against any article of the Constitution. He added, “We need to look at the Constitution of these three countries (Afghanistan, Bangladesh and Pakistan) in detail if we have to understand this Bill.”
Article 2 states in The Constitution of Afghanistan, he said, that Islam is the religion of the country and there are similar provisions in the Constitutions of Pakistan and Bangladesh.
Shah also said that religious atrocities have happened against Hindus, Sikhs, Christians, Parsis, Buddhists, Jains and other minorities in these three countries.
ALSO READ: Widespread Protests Against BJP’s Communal Citizenship Amendment Bill
He also said that the government is “not taking away rights from Muslims”, but aims to provide citizenship to religiously persecuted minorities “who have come to India”.
The Union Minister said that because “Muslims are in majority in these three countries”, so applying for citizenship on “grounds of religious persecution is out of the question”.
If a Muslim from these three countries applies for citizenship, it will be considered with an open mind. “The person, however, won’t get benefit of this amendment as the person has not faced religious persecution”, ANI quoted him as saying.
What Opposition said
Congress’s Adhir Ranjan Chowdhury called it “nothing but a targeted legislation against minority people”. Party leader Shashi Tharoor called it “an assault on the foundational values of our republic”.
Tharoor had on Monday also submitted a notice in the Lok Sabha to oppose the Citizenship (Amendment) Bill at the introduction stage, saying it “violates” the fundamental right to equality.
ALSO READ: What Is The Citizenship Amendment Bill?
Trinamool Congress’s Saugata Roy also opposed the introduction of the bill and said that if any community is left out of law, “it is violative of Article 14 of the Constitution of India”.
The Lok Sabha voted to allow the introduction of the bill, 293 ayes against 82 noes.
(With PTI inputs)


Pippa Middleton Steps Out In Jimmy Choo Sneakers and a Banana Republic Coat
by Katherine J Igoe- As spotted by Daily Mail, Pippa Middleton stepped out with son Arthur in a gorgeous fall outfit.
- The Jimmy Choo shoes and Banana Republic coat (in certain colors) are still available.
- Pippa's been nailing the style game recently, particularly in an Anna Mason gown.
You know that outfit you're searching for in the cooler fall months? You know, the one that makes you feel polished and chic and warm and layered and perfect? Well, I have come to tell you that this outfit does actually exist, and it was worn by the incredible Pippa Middleton.
Pippa was out on a walk with her son Arthur, as she often is, in a glorious burgundy wrap coat that's the perfect fall color.  BOOM—perfect ideal fall outfit, right there. And yes, it is shoppable.
According to Harper's Bazaar, the coat is Banana Republic and still available in gray and tan. I would love the burgundy, but the wrap coat is so in right now that the other colors are still perfect.
Harper's Bazaar also makes the very good point that Meghan Markle also favors this cut of coat quite a bit, so...twinning with Pippa Middleton and the Duchess isn't too shabby, is what I'm saying.
According to Daily Mail, the shoes are Jimmy Choo and actually have a subtle star print on the sole of the white sneakers, which I find to be gorgeous and a perfect twist on your classic white option.
Both items are under $300, and what's even better is that Banana Republic has a 40 percent off sale going on right now, making the coat even more affordable.
Here's the full look, in case you want to twin head to toe:
Inspired. Teach me your ways, Pippa!
For more stories like this, including celebrity news, beauty and fashion advice, savvy political commentary, and fascinating features, sign up for the Marie Claire newsletter.


Not many software systems are so self-evident that users won't occasionally need help to understand how something works.
The best way to learn a new system is by example. Fortunately as we are designing by example, we can use many of the same cases to provide a user friendly guide to the system.
Once a user has become familiar with the system, the most often need documentation to tell them how to do something new.
Lastly we can never completely remove the need for a dry reference document.
Example - How to - Reference


|
VA-API
2.6.0.pre1
|
Motion Vector and Statistics frame level controls. VAStatsStatisticsParameterBufferType for H264 16x16 block. More...
#include <va_fei_h264.h>
Public Attributes | |
| uint32_t | len_sp: 8 |
| length of search path | |
| uint32_t | search_path: 8 |
| motion search method definition 0: default value, diamond search 1: full search 2: diamond search | |
| uint32_t | sub_pel_mode: 2 |
| sub pixel mode definition 00b: integer mode searching 01b: half-pel mode searching 10b: reserved 11b: quarter-pel mode searching | |
| uint32_t | inter_sad: 2 |
| distortion measure adjustment for inter search SAD comparison 00b: none 01b: reserved 10b: Haar transform adjusted 11b: reserved | |
| uint32_t | intra_sad: 2 |
| distortion measure adjustment for intra search SAD comparison 00b: none 01b: reserved 10b: Haar transform adjusted 11b: reserved | |
| uint32_t | mv_predictor_ctrl: 3 |
| indicate if future or/and past MV in mv_predictor buffer is valid. 0: MV predictor disabled 1: MV predictor enabled for past reference 2: MV predictor enabled for future reference 3: MV predictor enabled for both past and future references | |
| uint32_t | ft_enable: 1 |
| forward transform enable 0: disable 1: enable, needs frame_qp or mb_qp input for transform | |
| uint32_t | intra_part_mask: 5 |
| luma intra mode partition mask xxxx1: luma_intra_16x16 disabled xxx1x: luma_intra_8x8 disabled xx1xx: luma_intra_4x4 disabled xx111: intra prediction is disabled | |
| uint32_t | ref_width: 8 |
| motion search window(ref_width * ref_height) | |
| uint32_t | search_window: 4 |
| predefined motion search windows. If selected, len_sp, window(ref_width * ref_eight) and search_path setting are ignored. 0: not use predefined search window 1: Tiny, len_sp=4, 24x24 window and diamond search 2: Small, len_sp=9, 28x28 window and diamond search 3: Diamond, len_sp=16, 48x40 window and diamond search 4: Large Diamond, len_sp=32, 48x40 window and diamond search 5: Exhaustive, len_sp=48, 48x40 window and full search 6: Extend Diamond, len_sp=16, 64x40 window and diamond search 7: Extend Large Diamond, len_sp=32, 64x40 window and diamond search 8: Extend Exhaustive, len_sp=48, 64x40 window and full search | |
| uint32_t | disable_mv_output: 1 |
| MVOutput. When set to 1, MV output is NOT provided. | |
| uint32_t | disable_statistics_output: 1 |
| StatisticsOutput. When set to 1, Statistics output is NOT provided. | |
| uint32_t | enable_8x8_statistics: 1 |
| block 8x8 data enabling in statistics output | |
Motion Vector and Statistics frame level controls. VAStatsStatisticsParameterBufferType for H264 16x16 block.


(WDM Version)
Summary
Introduction to WDM Driver Model
Introduction to the Toaster Sample
Building the sample
Installation
Testing
Filters
Device Parameters Subkey
Power Management
WMI
Event Tracing
Toastmon
Toaster Installation
Package
The Toaster sample provides a starting point for Windows® driver development. It contains annotated code to illustrate the functionality of bus driver, function driver, assorted class, device, and bus filter drivers, class-installer, and device-specific co-installer for a hypothetical Toaster bus and its devices.
Every device driver stack for a Plug and Play (PnP) device under the Microsoft® Windows® 2000 and later operating system typically comprises a bus driver, a function driver, and from zero to one or more filter drivers. These drivers must support Plug and Play, Power Management, and Windows Management Instrumentation (WMI) to provide a better user experience and greater satisfaction.
These buzzwords make sense if you have developed a driver for Windows 95 or Windows 98. But, a developer who has only worked on Windows NT® drivers might wonder: What are these things? Why do I need to worry about them? How do I implement them?
Imagine a system with a new type of PnP I/O bus called a toaster bus. A controller chip on the motherboard initializes and manages the bus. The bus has a couple of ports jutting out of the box into which you can plug your toasters.
To provide support for this bus on Windows NT 4.0, you must modify the HAL (hardware abstraction layer) to recognize and initialize the I/O bus during system boot and you must provide a set of HAL functions for scanning the bus and accessing the configuration space of the devices by other drivers. Next, you must write drivers for every type of toaster device that load along with the system, and then use the exported HAL functions to scan the bus to detect the device, read the I/O resource requirements, and configure and initialize the device. These drivers are loaded regardless of whether or not a particular toaster is plugged in.
If another driver requires the I/O resources claimed by your driver, there is no resource distribution mechanism on Windows NT 4.0 to instruct the driver to relinquish them and use other resources if possible. If you want to expose instrumentation data or report some exceptional events to user mode, you must provide your own interface and custom applications. There is no generic interface like WMI and no power management.
To support this bus and its devices under Windows 2000 and later OS, however, you don’t have to modify the HAL or export a new set of functions. All you need to do is write a bus driver that has knowledge of bus architecture, identifies (enumerates) devices on the bus, reads their resource requirements, and configures them. This driver model also makes the operating system independent of its I/O bus. This means you don’t need help from Microsoft if you design a new I/O bus to modify the HAL. Then, you write function drivers to control individual devices connected to the bus. Later on, one can write one or more filter drivers to add or modify the features supported by bus, a specific device or class of devices. There can be any number of lower-level or upper-level filter drivers for a bus, a device, or a class of devices.
The Windows Driver Kit documentation explains these new concepts and features by providing background information and describing how to implement them in your driver(s). This article and the accompanying sample drivers package provide annotated code samples that illustrate the functionality of various drivers without getting into detailed hardware specifics. These samples will help you start coding right away.
To make the sample code closer to a real-world driver, I have defined a new class of devices called the TOASTER class and wrote a bus driver, function driver, and all possible class, device, and bus filter drivers for this hypothetical TOASTER bus and its devices. I have also provided a sample of coinstaller DLL to show how you can parse a custom section from an INF file and perform some special operations before and after the installation of a device, and how you can create FriendlyName for a device. The function and bus driver also show how you can provide power manager and WMI support.
You can learn the implementation details of these sample drivers by looking at the code and reading the Windows 2000/XP/Server 2003 DDK documentation. The rest of this article discusses the contents of the package that accompanies this article and how to install, build, and test these drivers. This article also briefly examines the various registry entries created by the system to setup and load the drivers.
Note: This package is mostly intended to demonstrate WDM concepts for educational purposes. It is not to be used in a production environment in its entirety. One may not require all of the components of the package or all the features demonstrated in a single component to have a working driver.
This sample driver package contains bus, func, filter, inc, coinstaller, classinstaller, inf, toastmon, and toastpkg directories. The following summary describes the directories and key files.
bus
This directory contains the source code of the toaster bus driver (Busenum.sys). The job of this driver is to service the TOASTER bus controller, enumerate devices that are plugged in, and perform bus-level power management. The bus driver supports D0 and D3 power states. It also has a WMI interface.
func
All the sub-directories under this one contain the source code of the function driver (Toaster.sys) for standard toaster devices. To be illustrative and useful learning sample for beginners to driver development, the sample has been built from almost nothing (skeletal) to fully functional, adding useful features at each step. When built, all the different versions produce toaster.sys file. You can use the standard toaster.inf or toastco.inf to install and test. You can either manually install the driver (root-enumerations) or bus enumerate the driver using the toaster bus driver. They all share one common header file present in the shared directory. Let us assume that the function driver owns the power policy of the toaster device and supports D0, D1 and D3 power states, and also the toaster device is capable of waking the system from D1 state.
- Incomplete1: This is the simplest form of a WDM driver. It shows bare minimum functionality required to get installed and loaded in the system. You cannot open the device or talk to it. As the name suggests, this is not complete and safe enough to be used as a model for a production level driver.
- Incomplete2: This version is slightly advanced than the incomplete1 version. This version shows how to track I/O IRPs and handle stop and remove PNP request safely with respect to driver unload. Instead of using remlocks, this sample implements its own locking scheme to be more general purpose and compatible with 9x systems. You can open the registered interface from usermode and send read, write and IOCTL requests. This is a still an incomplete sample because it doesn't handle power IRPs and do the necessary S to D power IRP conversion required by the bus driver.
- Featured1: This is a complete version with full fledged power management and WMI support.
- Featured2: This version contains Wait-wake support and Event Tracing support in addition to all the features supported by featured1.
inc
This directory contains headers files that are shared among drivers and applications.
Disk
This directory is the build target path. All the toaster binaries are placed here during build under the respecive build_environment\target_OS sub-directories. For example, if you build under Windows Server 2003 x86 checked build environment, the target path will be disk\chk_wnet_x86\i386\. Since there are more than one version of toaster.sys, it is not placed in this directory to avoid overwriting one another. All the varoius versions of toaster.sys are built under their respective source directory.
filter
This directory contains six different subdirectories, each producing one of the following drivers from a common source file (filter.c):
o Class upper filter (clsupper.sys)
o Class lower filter (clslower.sys)
o Device upper filter (devupper.sys)
o Device lower filter (devlower.sys)
o Bus FDO upper filter (bfdoupr.sys)
o Bus FDO lower filter (bfdolwr.sys)
coinstaller
This directory contains source code of the device-specific coinstaller (tostrco1.dll). The DDK documentation has a good overview of coinstaller and its operation. The coinstaller demonstrates how to create a FriendlyName for a device based on its unique instance id. In this sample, during enumeration, the bus driver provides the serial number in the UINumber field of the device capabilities. The FriendlyName is required to uniquely identify multiple devices of the same interface class. The coinstaller also shows how to open an INF file and parse a custom section.
classinstaller
This directory contains source code of the class-installer (tostrcls.dll). The DDK documentation has a good overview of classinstaller and its operation. This dummy class-installer included to provide a class icon for all the TOASTER Class devices. It is copied to the system32 directory when the class is installed for the first time in the system.
inf
This directory contains 3 subdirectories (i386, amd64, & ia64) and each contains following files:
o bus.inf: This .inf installs the basenum.sys and sets up the registry.
o simple.inf: This .inf creates Toaster class, installs toaster.sys and sets up the registry.
o toaster.inf: This .inf file is functionally similar to simple.inf but also installs the class-installer. The class-installer provides custom icon for the class and an advanced property page to change the friendlyname of the device in the device manager.
o toastco.inf: This .inf file is functionally similar to toaster.inf but also installs the coinstaller. The co-installer is used to dynamically create a unique friendlyname of the device based on the serial number.
o busf.inf and toasterf.inf: These two .inf files are functionally similar to the above INF files but also install all the previously mentioned filter drivers.
o filter.inf: This .inf installs just a device upper filter for the toaster device. Please read the Filter section in this article on how to use this .inf file.
o toaster.cat: This is a dummy catalog file.
toastmon
This has the source of a root-enumerated driver called toastmon.sys. More information on this is covered later in the Toastmon section.
To build the sample drivers, you must first set up the DDK environment on your host machine. The “Installation and Release Notes” in the Windows Driver Kit has a complete description on how to do this.
1. Run the build –ceZ command in the Toaster directory to build all the binaries.
2. Copy all the binaries, a bus driver INF file (bus.inf), toaster.cat, and a toaster device INF file (toastco.inf) to a floppy disk or a temporary directory on the target system. Do not copy all the INF files.
3. Copy the device metadata package to a floppy disk or a temporary directory on the target system. Use the device metadata package in the ja-jp folder if the target system is in the Japanese locale. Otherwise, use the device metadata package in the en-us folder.
First install the bus driver. To install the bus driver on Windows 2000:
1. Double-click the ‘Add/Remove Hardware’ wizard in Control Panel.
2. At the Add/Remove Hardware Wizard, click Next.
3. Choose the ‘Add/Troubleshoot a device’, then click Next.
4. Select ‘Add a new device’ from the list, then click Next.
5. Select ‘No, I Want to Select the Hardware from a list’ and then click Next.
6. Select ‘System Devices’ and then click Next. NOTE: This might take a few minutes.
7. Click 'Have Disk', make sure that 'A:\' is in the "Copy manufacturer's files from:" box, and click OK.
8. Click on the desired of the two entries, and then click Next.
9. At 'Start Hardware Installation,' click Next.
10. Click Finish at 'Completing the Add/Remove Hardware Wizard.'
To install the bus driver on Windows XP and Windows Server 2003:
1. Double-click the ‘Add Hardware’ wizard in Control Panel.
2. At the 'Welcome to the Add Hardware Wizard', click ‘Next’.
3. Select 'Yes, I have already connected the hardware', then click Next.
4. Select ‘Add a new hardware device’ from the list, then click Next.
5. Select ‘Install the hardware that I manually select from a list(Advanced),' and then click next.
6. Select ‘System Devices’, then click Next.
7. Click 'Have Disk', make sure that 'A:\' is in the "Copy manufacturer's files from:" box, and click OK.
8. Click on the desired entry, and then click Next.
9. At 'The wizard is ready to install your hardware', click Next.
10. Click Finish at 'Completing the Add/Remove Hardware Wizard.'
To install the bus driver on Vista and later OS, use devcon.exe as shown below.
Another quick way to install the bus driver without going through so many mouse clicks would be to use the Installer sample application present in the src\tools\devcon directory. This sample allows you to root-enumerate a driver with one simple command. Please read the help file included in the sample on how to build and use the application to install this driver. To install the bus driver using devcon.exe:
c:\>devcon.exe install bus.inf "root\busenum"
The system copies the busenum.sys file to the %Systemroot%\system32\drivers directory and sets up the following registry keys to represent the bus driver to the PnP manager:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97D-E325-11CE-BFC1-08002BE10318}\nnnn
// nnnn is the instance number of this System Class driver on the system.It copies the INF file as OEM.n.INF, where n is a zero-based number, to the system INF directory. It also creates the standard Services keys to load the driver:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\busenum.
Once installed the system creates device registry keys (Hardware keys) under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\SYSTEM\nnnn
// nnnn is the instance number of this System Class driver on the system.
Once the Toaster bus driver is installed and started by the PnP Manager, you can run the enum.exe or Notify.exe application from the command prompt to simulate plug in, unplug or ejection of toaster devices on the system. Both these applications basically send an I/O control (IOCTL) to the bus driver with the user provided globally unique serial number and Hardware ID of the device, and trigger the entire enumeration process. The PnP manager takes the ID information provided by the bus driver and searches the system INF directory to find a matching INF file. If it doesn't find a suitable INF file (that would be the case when you install for the first time) it prompts the user to specify an INF file. At this point, you can pick one of the three INF files (toaster.inf, toastco.inf or toasterf.inf) to be the device INF file. If you are testing this sample for the first time, you should choose toastco.inf.
You can remove/eject a single device by giving its serial number or remove/eject all the devices by specifying 0 (zero) as the serial number of the device.
To plug in a device (or rather simulate a device arrival):
C:\>enum -p 1
To unplug a device:
C:\>enum -u 1
To eject a device:
C:\>enum -e 1
To test a plugged in device, you can use the toast.exe application. This application basically enumerates all the toaster class devices, displays its properties such as FriendlyName, InstanceId, and opens the last enumerated device to perform a read operation and send a DeviceIoControl to the device depending on the user command line option.
If you invoke without any option it basically opens the last enumerated interface and prompts you to initiate a Read operation in a loop. You press any key to continue the read loop or press ‘q’ to break out of the loop. If you use the –h option it opens the last enumerated interface and sends a DeviceIoControl to hide the device from the Device Manager before performing read.
Usage: Toast {-h option causes the device to hide from Device Manager UI}
Both these applications use the SetupDi functions to enumerate and open the device interfaces. These functions are documented in the Windows 2000/XP/Server 2003 DDK documentation.
You can install device filter drivers by specifying LowerFilters or UpperFilters to the Hardware registry key (HKLM\ \SYSTEM\CurrentControlSet\Enum) for the device; and class filters by specifying them to the Software registry key (HKLM\SYSTEM\CurrentControlSet\Control\Class\) for the device class.
Because this is an MULTI_SZ string, you can specify more than one filter for the device or class. If you specify more than one, the load order is in the order they are listed – the filter at the end of list is the topmost driver in the stack, and so on. However filter drivers should not be written to rely on this order, because the load order can change and other filter drivers may or may not be there in the group. You can install device specific filters by using a [.HW] section that specifies AddReg section, and class specific filters by specifying AddReg section from the base install section in your INF file. The busf.inf and toasterf.inf show how to do that.
The filter.inf file is a special .inf file that enables you to install a filter driver for the toaster device after it has been installed and enumerated. To install an upper device filter for a toaster device on Windows 2000:
1. Enumerate a toaster device.
2. Open the Device Manager.
3. Open the Properties of the Toaster device for which you want to install filter.
4. Click the Driver tab, and then click Update Driver.
5. Follow the wizard's prompts, and when prompted, select the Display a list of the known drivers option.
6. Click Have Disk and point to the location of the filter.inf file.
7. Proceed through the rest of the install.
Currently the sample doesn’t show how to read Device Parameters value from the registry. This feature will be added in the future updates of this driver.
Under Windows 2000/XP/Server 2003, the configuration information is not stored under the Services key of the driver. It is stored in three different places, depending on whether it’s device instance specific, driver specific or interface specific.
You can store device-specific configuration information under the Hardware key of that particular device instance (HKLM\SYSTEM\CCS\Enum\<DeviceId>\<VendorId>\<InstanceId>\Device Parameters) and driver-specific information under the Software key (HKLM\SYSTEM\CCS\Control\Class\<GUID>\<driver-instance-id>\ Device Parameters) of the driver by using IoOpenDeviceRegistryKey function.
You can store interface-specific information under the device-interface key (HKLM\SYSTEM\CurrentControlSet\Control\DeviceClasses\{GUID}\<SymbolicLinkName>\Device Parameters) by calling IopenDeviceInterfaceRegistryKey with the symbolic link name of the device interface. Both of these functions return the handle to the Device Parameters subkey. For legacy support, you can continue to store information under the Services key.
In this example, the function driver acts as a power policy owner for the toaster device and supports DO and D3 power mode. You can use the same power logic to implement power policy in the bus driver. You need a system with an ACPI-compatible BIOS in order to test the power management code. If you have an ACPI compatible system, you will see a Standby option in the Shutdown submenu.
Following paragraphs illustrate how the funcion driver handles various power requests (power.c). The graph below shows the order in which various functions are called in each case. For clarity, the word Toaster has been removed from all the function names.
Query Power Request (IRP_MN_QUERY_POWER):The function driver first sends the system query power IRP (S-IRP) down to the bus driver and when the IRP gets completed, it generates a device query power IRP (D-IRP) in the completion routine. The S-IRP is marked pending and saved in the FDO device-extension. The function driver then receives the newly generated D-IRP as it gets sent from the top of the stack by the power manager. If the device is going into a low power state, it marks the queue state to hold any incoming requests, waits for the all the pending I/Os to complete, and forwards the D-IRP down to the bus driver. When the bus driver completes the IRP, the power manager calls the power IRP completion routine. Here, in the power IRP completion routine, the function driver completes the S-IRP.
DispathPower (S-IRP)
|
|---->DispatchQueryPowerState
|
|---->DispatchSystemPowerIrp
|
|---->PoCallDriver to Busdriver
|
CompletionSystemPowerIrp*<----|
|
|---->QueueCorrespondingDeviceIrp (1)
|
|---->DispathPower (D-IRP)
|
|---->DispatchQueryPowerState
|
|---->DispatchDeviceQueryPower (2)
|
|---->FinalizeDevicePowerIrp
|
|---->PoCallDriver to Busdriver
|
CompletionOnFinalizedDeviceIrp**<----|
|
|---->IoCompleteRequest (S-IRP)
Set Power Request to Power-Down(IRP_MN_SET_POWER): The function driver first sends the S-IRP down to the bus driver and when it completes, it generates a D-IRP in the completion routine. The S-IRP is marked pending and saved in the FDO device-extension. The function driver then receives the newly generated D-IRP as it gets sent from the top of the stack. If the device is going into low power state, it saves the device context, powers down the device and then forwards the D-IRP down to the bus driver. When the bus driver completes the IRP, the power manager calls the power IRP completion routine. Here the function driver completes the S-IRP.
DispathPower (SIRP)
|
|---->DispatchSetPowerState
|
|---->DispatchSystemPowerIrp
|
|---->PoCallDriver to Busdriver
|
CompletionSystemPowerIrp*<----|
|
|---->QueueCorrespondingDeviceIrp (call PoRequestPowerIrp to generate D-IRP)
|
|---->DispathPower (D-IRP)
|
|---->DispatchSetPowerState (D-IRP)
|
|---->DispatchDeviceSetPower
|
|---->CallbackHandleDeviceSetPower (3)
|
|---->FinalizeDevicePowerIrp
|
|---->PoCallDriver to Busdriver
|
CompletionOnFinalizedDeviceIrp**<----|
|
|--->IoCompleteRequest (S-IRP)
Set Power Request to Power-Up(IRP_MN_SET_POWER): The function driver first sends the S-IRP down to the bus driver and when it completes it generates a D-IRP in the completion routine. The S-IRP is marked pending and saved in the device extension. The function driver then receives the newly generated D-IRP as it gets sent from the top of the stack. If the pending S-IRP is for restoring the power state of the system to S0, the driver first completes the S-IRP and then if the device is in a low power state, it powers up the device, restores the device context and processes any pending IRPs waiting in the queue. The reason the S-IRP is completed before the D-IRP during power-up is to speed-up the system resume as restoring the device to Do usually takes longer. One thing to note here is that to avoid receiving remove IRP from PNP manager, you must first request D-IRP and then complete the S-IRP, You shouldn't do that in reverse order because the PNP manager guarantees that as long as an S-IRP is pending, it will not send a remove request. Then the function driver forwards the D-IRP down to the bus driver. When the bus driver completes the IRP, the power manager calls the power IRP completion routine. Here the function driver completes the S-IRP.
DispathPower (SIRP)
|
|---->DispatchSetPowerState
|
|---->DispatchSystemPowerIrp
|
|---->PoCallDriver to Busdriver
|
CompletionSystemPowerIrp*<----|
|
|---->QueueCorrespondingDeviceIrp (call PoRequestPowerIrp to generate D-IRP)
|
|---->DispathPower (D-IRP)
|
|---->DispatchSetPowerState (D-IRP)
|
|---->DispatchDeviceSetPower (Complete S-IRP)
|
|---->PoCallDriver to Busdriver
|
CompletionDevicePowerUp*<----|
|
|---->CallbackHandleDeviceSetPower (4)
|
|---->FinalizeDevicePowerIrp
|
|---->IoCompleteRequest (D-IRP)
|
|---->CompletionOnFinalizedDeviceIrp**
* - This is an IRP completion routine set using IoSetCompletionRoutine.
** - This is a Power IRP completion routine specified in PoRequestPowerIrp when we generate D-IRP.
The difference is that the IRP completion routine is called by the I/O manager when the lower driver calls IoCompleteRequest but the power IRP completion routine is called by Power manager, just before freeing the IRP memory, when the IRP finally returns back to it.
1. Calls PoRequestPowerIrp to generate D-IRP and sets CompletionOnFinalizedDeviceIrp as the power IRP completion routine.
2. If the system is going to lower power state, start queuing requests.
3. This is a worker thread spawned to run at PASSIVE_LEVEL. Here, save the device-context and power-down the devie.
4. This is a worker thread spawned to run at PASSIVE_LEVEL. Here, power-up the device and restore device context. If there are IRPs pending in the queue process them.
A WMI interface is provided to both the function and bus driver. The WMI library is used to handle WMI IRPs. The MOF files, which define WMI data and event blocks, are compiled along with the driver and included in the driver’s binary image.
To test the WMI interface, first install the WMI SDK on your system. Then, use either wbemtest.exe or CIM Studio to enumerate the instances registered by these drivers.
For example, to see the data exported by the Toaster driver:
1. Run wbemtest.exe.
2. Connect to “root\WMI” class.
3. Click Enum Instances.
4. Type ToasterDeviceInformation and press Enter.
You should see the toaster device instances. The DebugPrintLevel data in both the drivers have been made read/write, so that it is possible to dynamically change the value of these variables with the WMI application and control the driver debug trace seen on Windbg.
You can also generate a HTML script using the bmf file (wmimofck -whtml toaster.bmf) and test both the data and event blocks exported by the driver. The toaster driver fires a ToasterNotifyDeviceArrival event every time a device is plugged in and started successfully. For more information on WMI testing, check http://support.microsoft.com/support/kb/articles/q252/6/79.asp. The function driver's WMI handler also responds to WMI queries from Device Manager to provide Power Manangement tab in the device properties dialog.
Event tracing in Windows (aka software tracing) allows drivers to log debug trace messages efficiently without affecting system performance. You can selectively enable tracing on your target machine and log messages. You can do the tracing both on free and checked build system without requiring a kernel-debugger or serial connection. You can watch the traces simultaneously in the target machine and also in the kernel-debugger. The steps required to provide software tracing is fairly easy and documented in the DDK "WPP Software Tracing" section. These are the following things I did to get tracing support in toaster function driver.
1. Generated a GUID (C56386BD-7C67-4264-B8D9-C4A53B93CBEB) using GUIDGEN. This GUID will be used as the control Guid (provider guid) for toaster.
2. Defined the debug flags and GUID in a header file (toaster.h). Look for WPP_CONTROL_GUIDS.
3. Included a file called xyz.tmh, where xyz is name of the source file, in every source file after all other includes files and before any WPP macros are called.
4. Registered for tracing in DriverEntry by calling WPP_INIT_TRACING(DriverObject, RegistryPath).
5. Deregistered for tracing in ToasterUnload by calling WPP_CLEANUP(DriverObject).
6. Added RUN_WPP=$(SOURCES) line to "sources" file to pre-process the WPP macro and generate xyz.tmh files.
7. Informed RUN_WPP to map all my ToasterDebugPrint calls to native DoTraceMessage function by using the func: option in RUN_WPP preprocessor directive.
Through out the code, you will see different implementation for enabling tracing on Windows 2000. This is due to the fact that tracing enable/disable is handled via IRP_MJ_SYSTEM_CONTROL dispatch handler in Win2K and via an explicit callback in XP and beyond. So if you have your own WMI handler, you have to add few extra WPP macros to workaround the issue. This also has an unavoidable side-effect that drivers on Win2K can be traced only if they have a device object. So, for WDM drivers that typically create their deviceobject in AddDevice, it's not possible to trace DriverEntry calls.
Logging the traces in a file:
1. Generate Trace message format (.TMF) files from the toaster.pdb file. You can do that by calling "tracepdb -f toaster.pdb" in the DDK build environment. This command will produce two files, C56386BD-7C67-4264-B8D9-C4A53B93CBEB.tmc and yyy.tmf, where yyy is some guid, for every source file that makes the ToasterDebugPrint tracing call.
2. Copy all the tmf files to the target machine in a temporary directory, say c:\temp.
3. Install the toaster driver.
4. Copy all the tracing tools from %DDKROOT%\tools\tracing directory to your target machine's temp directory.
5. Create a text file called toaster.ctl, and add the following line, "C56386BD-7C67-4264-B8D9-C4A53B93CBEB toaster".
6. Set TRACE_FORMAT_SEARCH_PATH environment variable to point to the directory where the TMF files are present. In our case, it is c:\temp.
7. Enable debug tracing by calling "tracelog -start -guid toaster.ctl -f toaster.bin -flags 0x1"
8. Force the driver to do something. You can either disable/enable or run toast.exe and send read requests. All the debug messages will be logged in toaster.bin file in a binary form.
9. Stop the logger by calling "tracelog -stop toaster"
10. Finally, format the binary log file to get human readable text file by calling "tracefmt -nosummary toaster.txt toaster.bin".
Note that you can also get realtime traces by using the -rt option of tracelog at the time you enable the tracing. You can also use the TRACEVIEW (src\tools\traceview) utility from the DDK to get the traces easily. This GUI tool has been built around the other tracing utilities mentioned above to make the task of getting traces a lot easier.
Getting the traces in realtime on the host machine and in kernel debugger:
1. Enable realtime tracing on the target machine with -kd option.
c:\temp>tracelog -start toaster -rt -kd -ft 1 -guid toaster.ctl -flags 0xff
2. On the host-side, in the kernel debugger, turn on dynamic printing by using !WMITRACE debugger extension.
kd>!wmitrace.dynamicprint 1
3. Then, set the WMI trace search path to the directory that contains all the TMF files generated earlier.
kd>!wmitrace.searchpath path_of_TMF_files
4. Also make sure that !wmitrace.guidfile is set to default.tmf or system.tmf depending on where you have that file in relation to the debugger.
5. If the tracing is enabled, you should see a 'toaster' session entry listed when you dump the event trace structures.  You can view the traces in realtime on the target machine by running:
tracefmt.exe -rt toaster -p path_of_TMF_files -display
Please note that !wmitrace debugger extension is not supported on Win2K. So you wouldn't able to see the traces of a Win2K system in a kernel debugger.
This driver demonstrates how to handle PnP notification in kernel-mode. Using the toastmon.inf file you can install this driver with Add Hardware wizard. This driver gets root-enumerated and in its AddDevice, it registers for device arrival notification on the Toaster interface class. When you plugin a toaster device, the system calls the notification handler and the driver opens the associated device and registers for Device Change notification. When you disable/unplug/eject the toaster device the driver notification handler is called to close handle to the device. The technique demonstrated in this sample is useful when you write a driver that wants to talk to a device that your driver is not controlling.
© Microsoft Corporation 2002


We run weekend kayaking trips to exotic locations around the South Island of NZ. Think Tekapo, Hawea, Rangitata. Beutiful. Here are some photos:
Contact Us
theoucc(at)gmail(dot)com
Can't work this out? That's ok, the tramping club will have you.
Basics
Semester One. Most of our activity happens during the first 6 weeks of semester 1 each year (Feb-May). We find that after the mid-semester break, the water gets colder, and students start to have real work to do.
If you've missed it, you can still email us and have a chat, but the trips aren't as often.
However, if it's before or DURING semester one, email NOW. It's over so quickly, and it's easy to miss out if you don't act.
You can still become a member later on in the year. We often take the boats out the the various beaches around Dunedin, and there are a few big trips around the Island.
Websites are funny things. If you want the latest info, head over to our Facebook page. No, seriously, the stuff here is good info, but you REALLY want to check that out.
So.. what do you do? Canoeing?
Um.. No. It's really just whitewater kayaking. The name is a vestige of our history and we love the acronym. Plus all our gear has "OUCC" stamped on it, so we just kept the name.
How does it work?
You join up, pay your membership fee, Number one goal for you is to get onto our mailing list for the year. You can do that by sending a friendly email to theoucc(at)gmail.com (we ) We send an email out early in the week, usually Tuesday night, about the upcoming trip that weekend. Start thinking about whether you can come.
On Thursdays at around 1:30pm, we have a trip meeting in the Clubs and Socs Building. (pic).
This is where we give you a bit more information and you put your name on the trip list. We only have so much gear, so it's first come, first served.
On Friday afternoon, we all meet at the gear shed around the back of Clubs and Socs, and you pick out all your gear.
We leave after this so make sure you have everything you want for the weekend.
You need a helmet, paddle, lifejacket, spray deck, and of course, a kayak. Make sure you have all this stuff. Talk to a member of the Exec for help.

We then pack all the gear onto the trailer. (pic) Please help as much as possible with this. EVen if you can';t tie knots (you should probablky learn) you can help lift boats onto the trailer.
Once the trailer is loaded and all tied down, we allocate people into cars or vans and set off on our adventure. This is normally about 6:30, so we generally stop somewhere for dinner. Some of the campping spots are a long way from Dunedin so it's often dark when we get there. Bring a torch.
Sounds good, how much do I owe you?
We try to keep all trips as cheap as possible.Membership:
$60 if you don't have your own kayaking gear, you can borrow ours all year. $30 if you have your own paddling gear
Trip Cost:
Around $20-30 each trip.
This depends how far we have to drive and what the camping situation is like.
This fee pays for petrol for the vehicles, van hire, and accomodation.
I'm scared. I don't know anyone else going.
That's all you're worried about? This is consistently the friendliest bunch of people in Dunedin. You have a 2+ hour van ride to meet people before we even get there, so it'll be fine.
What should I bring?
Pack what you'd take to a 2 day camping trip at a place with no power or running water. Which could be sunny and hot or rainy and cold. This is New Zealand. Still need ideas? - Tent - Sleeping bag - Bed roll - Food for 2x breakfasts, 2x lunches, and 1x dinner - Alcohol for Saturday night - Torch, preferably a headlamp - Baking Clothes - Some warm gear for the nights - Clothes for kayaking in. Generally a wetsuit is advisable. Good paddlejackets are also fine. - Bring plenty of polyprops. - Jandels for wearing around camp and in your boat. We often walk over rocks to get in and out of the water, so some shoes that can get wet are a good idea.What should I expect?
Once we get to the camping spot on Friday night, we set up camp and go to bed.
Everyone's split into groups under instructors and they will look after you.
On Saturday, we generally do a morning paddle, come back to the campsite for lunch, then set off for an afternoon paddle somewhere.
After our last run for the day, we settle down at the campsite for dinner. What happens after this varies widely but usually involves the consumption of a good amount of alcohol and the having of a lot of fun. We're normally in the middle of nowhere with no other groups around, so anything can happen.
Sunday morning. Everyone gets up, some reluctantly, and we do another kayak run somewhere. After that's finished, we go back to the campsite, pack everything up and load the trailer, and set off back to Dunedin.
We generally get back to the gear shed around 6pm, but it depends on the trip.
What's this Murchison thing everyone gets so excited about?
Murchison is a sleepy little town in the north of the South Island that happends to be crawling with amazing rivers for kayaking. The NZ Kayak School is based here. Every year, in the mid-semester break, the club goes up to Murchison.
I've never kayaked before!
That's fine. Most of our members aren't strong kayakers when they start. We teach you how to kayak.
I can't eskimo-roll!
That's fine. Rolling isn't essential but the longer you stay dry, the more fun it is. We hold rolling sessions up at Moana Pool in the mornings, twice a week, Wednesdays and Fridays, until May, which you should come to and learn. It's a lot easier to learn in a heated pool, and our instructors are very helpful. Plus, you can hang out in the spa afterwards!
I can't swim
Ooh. Well, we give you a lifejacket so you will definitely float, and the point is to STAY in the kayak, but most beginners fall out of their boats a couple of times. Come up to a rolling session and see if you're comfortable. Or learn to swim really quickly so you can come on the trips.
Is it safe?
Yes. As casual as may seem, we take safety very seriously. Most of the work goes on behind the scenes. We have very experienced instructors, and the rivers we paddle on are generally not very dangerous. Just wear your helmet and follow instructions. It seems a lot scarier than it is.
I'm a Grade III + paddler. Would I get any benefit from coming?
If you're really good, you probably won't be challenged much on most of the weekend trips. Tekapo has a surfing hole, and Murchison has advanced runs. We try to do a few harder runs each trip but it doesn't always happen. We'd love to have you though. You could help the beginners and, of course, off the water is where the real fun begins.
Where in NZ do you go?
This depends on the year but our main haunts are: - Andersons Bay (introductory day) - Tekapo (river and slalom course) - Hawea - Beaumont - Rangitata - Mavoura Lakes - Murchison (week long trip in the April holidays)
There are a few others that we sometimes got to, but these have proven to be the most fun and reliable.


Presentation of
Your project
Your baseline here — created by [your name here].
2015 - @Washaweb — Built with Transition.js — MIT License — get more transitions
Your baseline here — created by [your name here].
2015 - @Washaweb — Built with Transition.js — MIT License — get more transitions
Use a text slide markup content to create titles slides.
This is a sample slide for demonstration only.


list_to_u8array(xs)
list_to_s8array(xs)
list_to_u16array(xs)
list_to_s16array(xs)
list_to_u32array(xs)
list_to_s32array(xs)
list_to_u64array(xs)
list_to_s64array(xs)
Return a u8/s8/u16/s16/u32/s32/u64/s64array with all the elements of the list xs
.
The list must contain only integer values.
list_to_u8array([12, 123, 45])
// #u8[12, 123, 45]


Represent a background environment with atmospheric scattering. The sun direction can be animated.
More...
#include <Sky.hpp>
|
| enum | Type : int { Common = 0,
PBRRegular,
PBRParallax,
PBRNoUVs
} |
| | Type of shading/effects. More...
|
| |
|
const Mesh * | _mesh = nullptr |
| | Geometry of the object.
|
| |
|
std::vector< const Texture * > | _textures |
| | Textures used by the object.
|
| |
|
std::vector< std::shared_ptr< Animation > > | _animations |
| | Animations list (applied in order).
|
| |
|
Animated< glm::mat4 > | _model { glm::mat4(1.0f) } |
| | The transformation matrix of the 3D model, updated by the animations.
|
| |
|
Type | _material = Type::Common |
| | The material type.
|
| |
|
bool | _castShadow = true |
| | Can the object casts shadows.
|
| |
|
bool | _twoSided = false |
| | Should faces of the object be visible from the two sides.
|
| |
|
bool | _masked = false |
| | The object RGB texture has a non-empty alpha channel.
|
| |
Represent a background environment with atmospheric scattering. The sun direction can be animated.
- See also
- Atmospheric scattering
Inherits Object.
◆ Sky()
Constructor.
- Parameters
-
| mode | the storage mode (CPU, GPU, both) for the internal data. |
◆ decode()
Setup a sky environment parameters from a list of key-value tuples. The following keywords will be searched for:
bgsky:
direction: X,Y,Z
animations:
...
- Parameters
-
| params | the parameters tuple |
| mode | the storage mode (CPU, GPU, both) |
Reimplemented from Object.
◆ direction()
| const glm::vec3& Sky::direction |
( |
| ) |
const |
|
inline |
Reference to the sun direction.
- Returns
- the normalized sun direction
◆ encode()
Generate a key-values representation of the object. See decode for the keywords and layout.
- Returns
- a tuple representing the object.
Reimplemented from Object.
◆ update()
| void Sky::update |
( |
double |
fullTime, |
|
|
double |
frameTime |
|
) |
| |
|
overridevirtual |
Apply the animations for a frame duration.
- Parameters
-
| fullTime | the time since the launch of the application |
| frameTime | the time elapsed since the last frame |
Reimplemented from Object.
The documentation for this class was generated from the following files:
- src/engine/scene/Sky.hpp
- src/engine/scene/Sky.cpp


Alchemist Matild:
All right, just as before you must gather the ingredients on this list... I don't need to explain it to you again, do I?


--- layout: default title: Home ---
Hi there! Welcome to my blog
Start from the navigation bar to know more about me. ^1000 Cheers : ) Click here for my Imperial Homepage


The standard unit of energy is the Joule.
W = F → ⋅ x → Joules (J)
W = ΔKE = -ΔPE J
PEgrav = m g h J
KE = 12 m dxdt 2 J
F t = m d2x dt2 J
P = dW dt J s -1


import {MatCardModule} from '@angular/material/card';
MatCard
A basic content container component that adds the styles of a Material design card.
While this component can be used alone, it also provides a number of preset styles for common card sections, including:
Selector: mat-card
Exported as: matCard


bool mysqli_report ( int $flags )
mysqli_report() is a powerful function to improve your queries and code during development and testing phase. Depending on the flags it reports errors from mysqli function calls or queries which don't use an index (or use a bad index).
Returns TRUE on success or FALSE on failure.


Malappuram (also Malapuram) (About this soundpronunciation) is a city[7] in the Indian state of Kerala, spread over an area of 58.20 km2 (22.47 sq mi). The first municipality in the district formed in 1969, Malappuram serves as the administrative headquarters of Malappuram district. Divided into 40 electoral wards, the city has a population density of 1,742 per square kilometre (4,510 per square mile). According to the 2011 census, Malappuram metropolitan area is the fourth urban agglomeration in Kerala and the 25th largest in India with a total population of 1.7 million.[8] It is the fastest growing city in the world with a 44.1% urban growth between 2015 and 2020 as per the survey conducted by Economist Intelligence Unit (EIU) based on the urban area growth during January 2020.[9][10] Malappuram is situated 54 km southeast of Calicut and 90 km northwest of Palakkad.[11] It is the first Indian municipal body to provide free Wi-Fi connectivity to its entire residents.[12][13] Malappuram is also the first Indian municipal body to achieve the International Organization for Standardization certificate.[14] It is also the first complaint-free municipality in the state.[15]
Chamakkayam Riverside Park
Kottakkunnu
Sri Maha Vishnu Temple
shanthitheeram Park


Reports lines that are longer than the
Hard wrap at
parameter specified in
Settings | Editor | Code Style | General
.


WITNESS LIST Natural Resources Committee March 21, 2001-3:00P HB 1389 For: Edmondson, Eddy (Texas Nursery & Landscape Association) Harden Jr., James (Mortellano's Nursery Inc.) On: Miller, Douglas (Doug) (Edwards Aquifer Authority) HB 1540 For: Barrett, Andy (Glenn & JoLynn Bragg) Bragg, Glenn (Bragg Pecan Farms Inc.) Bragg, JoLynn (Bragg Pecan Farms Inc.) Schmidtke, Gary (Self and Texas Pecan Growers Association) Storey, J. Benton (Self and Texas Pecan Growers Association) On: Ellis, Greg (Edwards Aquifer Authority) Miller, Douglas (Doug) (Edwards Aquifer Authority) HB 1842 For: Allen, Joe B. (West Harris County Steering Committee & H.C. MUD 102) Box, Jim (Harris-Galveston Subsidence District) Sallee, Daniel H. (Self and West Harris County Surface Water Steering Committee) HB 1909 For: Lange, Allan (Self and Lipan-Kickapoo W.C.D.) HB 2362 For: Sadler, Judge Alan (Montgomery County Commissioners Court) HB 2379 For: Adams, Thomas L. (City of San Angelo) HB 2403 For: Baker, Carole D. (Harris-Galveston Coastal Subsidence District, American Water Works Association) Gregg, Tony (Self and American Water Works Association) Against: Casey, Richard (Self and Alliance Laundry Systems) Guerrero, Patrick (McNairs Appliance Company) Nestle, Dan (Self and G.E. Appliances) Samuels, Charles (Association of Home Appliance Manufacturers) Wester, Mike (Coinmach Corporation) HB 2404 Against: Mintz, David (Texas Apartment Association) HB 2409 For: Edwards, Paul (Self and Uvalde County Underground Water Conservation District) Hilderbran, Vic (Uvalde County Underground Water Conservation District) Against: Rimkus, A. Maurice (Self) HB 2529 For: Fuller, Windi (Lone Wolf Groundwater Conservation District) Stubblefield, David (Lone Wolf Groundwater Conservation District) HB 2665 For: Lackner, Robert (Southmost Regional Water Authority) HB 2699 For: Clifton, Jr., William L. "Bill" (Self) Garrett, Ricky (City of Waco) Olson, Charles (Self and City of Meridian) Pertile, Arthur (City of Waco, Texas) Against: Albrecht, Ashley (Self) Coulter, Denise (Dublin Economic Development Corporation) De Jong, Donald (Self and CALM/TAD) Harris, Mitchell (Self) Price, Paul T. (Coalition for Affordable Local Milk) Terrell, James (Texas Association of Dairymen) Traweek, James (Self and Jam-Dot Dairy) Turley, Darren (Self and Erath County Farm Bureau) Vander Horst, Alan D. (Self) On: Hoffman, Margaret (TNRCC) Wallace, R.E. "Bob" (The Wallace Group) Registering, but not testifying: For: Graham, Jonathan (City of Temple) Igo, Shanna (Texas Municipal League) Against: de Uries, Jan Pieter (Self) Albrecht, Liz (Self) Arnold, Bruce (Self) Bramlett, Donnie (Self) Broumley, Keith (Self) Brugman, Bennie (Self) De Jong, William (Self) Geijsel, Arjen (Self) Grimes, Charles R. (Self) Hess, Myron (National Wildlife Federation) Konkhuis, Henk (Self) Loving, Carson (Self) Lueck, Sr., Fred (Self) Maberry, Angie (Self) Miller, Terry (Self) Nadine, Colbach (Self) Oosten, Gerald (Self) Pair, Kirby (Self) Pair, Mary K. (Self) Reilly, Frank (Coalition for Affordable Local Milk) Sargent, Garland (Self) Schouten, Nova (Self) Schouten, Zeba (Self) Talsma, Klaas (Self) Thompson, Joe B. (Self) Traweek, John (Self) Traweek, Ricky (Self) Turley, Deanna (Self) Vam der Laan, Pieter (Self) Vandermeer, Steve (Self) Volleman, Marcel (Self) Webb, Sherry (Self) Zwart, Durk (Self) On: Howe, Billy (Texas Farm Bureau) Rascoe, Zoe (TNRCC) HB 2847 For: Ray, Tom (Brazos River Authority) HB 2855 For: Bowlin, Stovy (Southeast Trinity Groundwater Conservation District) Millikin, Jay P. (Comal County) HB 2947 For: Gillett, Steve (City of LaPorte) On: Hess, Myron (National Wildlife Federation) HB 3404 For: Edmondson, Eddy (Texas Nursery & Landscape Association) Harden Jr., James (Mortellaro's Nursery) On: Ellis, Greg (Edwards Aquifer Authority) Miller, Douglas (Doug) (Edwards Aquifer Authority) HB 3562 For: Olson, Charles (Self) Pertile, Arthur (City of Waco, Texas) Against: Albrecht, Ashley (Self) De Jong, Donald (Self and CALM\TAD) Harris, Mitchell (Self) Price, Paul T. (Coalition for Affordable Local Milk) Terrell, James (Texas Association of Dairymen) Traweek, James (Self and Jam-Dot Dairy) Turley, Darren (Self and Erath County Farm Bureau) Turley, Deanna (Self) Vander Horst, Alan D. (Self) On: Hoffman, Margaret (TNRCC) Vickery, Mark (TNRCC) Registering, but not testifying: For: Hess, Myron (National Wildlife Federation) Igo, Shanna (Texas Municipal League) James, Reggie (Consumers Union Southwest Regional Office) Kramer, Ken (Lone Star Chapter of the Sierra Club) Against: Albrecht, Liz (Self) Arnold, Bruce (Self) Bramlett, Donnie (Self) Broumley, Kieth (Self) Brugman, Bennie (Self) De Jong, William (Self) Geijsel, Arjen (Self) Grimes, Charles R. (Self) Howe, Billy (Texas Farm Bureau) Konkhuis, Hank (Self) Loving, Carson (Self) Maberry, Angie (Self) Miller, Terry (Self) Nadine, Colbach (Self) Oosten, Gerald (Self) Pair, Kirby (Self) Pair, Mary K. (Self) Reilly, Frank (Coalition for Affordable Local Milk) Schouten, Nova (Self) Schouten, Zeba (Self) Talsma, Klaas (Self) Thompson, Joe B. (Self) Traweek, John (Self) Traweek, Ricky (Self) Vander Neer, Steve (Self) Volleman, Marcel (Self) Webb, Sherry (Self) On: Stokes, Kenneth W. (Self) SB 289 For: Parker, Linda A. (Small Hydro of Texas, Inc.) On: Ellis, Greg (Edwards Aquifer Authority) Sidnell, Jennifer A. (TNRCC) Silverstein, Alison (Public Utility Commission of Texas)


@* * Copyright 2021 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import uk.gov.hmrc.play.views.html.helpers.form @import helpers.{errorSummary, input} @import models.TakeoverDetails @import views.helpers.TitleHelper.title @(businessName: Form[String])(implicit request: Request[_], messages: Messages, appConfig: config.FrontendAppConfig) @main_template(title = title(messages(s"page.takeovers.otherBusinessName.title"),businessName)) { @messages("common.button.back") @errorSummary( Messages("common.errorSummary.label"), businessName, dataJourney = Some("TakeOvers") )
@messages("page.takeovers.otherBusinessName.paragraph")
@form(action = controllers.takeovers.routes.OtherBusinessNameController.submit()) {


Choose the Course
Our Courses
See What we do
About Testing Shastra
Pune's first ever training institute who believes in Hans-On
Training..
Our Success Story
Our Achievement
Enroll Now
Further and higher education colleges
These colleges offer courses and qualifications in a wide range of vocational and academic subjects at many levels.
General faq
Testimonial
Our Students are
Placed at


Customizing Working Directory Tracking
When DIScover processes a build log, cd commands assist in correct source code parsing. By default, DIScover automatically recognizes cd commands and gmake notations of “Entering directory ... Leaving directory”; however, some build logs use different commands to indicate the working directory. If your build log uses a working directory command that DIScover did not recognize during the model build process, you can modify TrackWorkingDirectory.pl to correct this.
TrackWorkingDirectory.pl contains a function (TrackWorkingDirectory) that scans a line from your build log, and if that line deals with the working directory, DIScover marks it with one of the following tags:
Note: All remaining lines in TrackWorkingDirectory.pl are left unmodified.
• A line output with a ~cd~ tag begins with ~cd~ and the remainder of the line consists of a space and the name of the new working directory.
• The ~pushd~ and ~popd~ tags track the working directory, in case the build log has a pop command that requires a stack for correct tracking. The ~pushd~ tag is followed by the name of a working directory, while the ~popd~ tag does not require one.
TrackWorkingDirectory.pl takes one argument (a build log line) and returns either the tagged line or the original, unmodified line.


They are different from you and me, this generation born after 1970. They grew up with a finger on the keyboard and an ear to the cell phone, and in a world where the forces of globalization have broken down national barriers like no time in history.
And right now this group is moving up in the business ranks, becoming managers, partners, and eventually CEOs. Chances are you manage employees from this generation, and it's not far-fetched to believe you may yourself be managed by them before you check out of your career.
If the book Got Game: How the Gamer Generation is Reshaping Business Forever is correct, the "gamer generation" will make very different kinds of employees and managers.
Is that a bad thing? They are loners, after all. Right? That can't be a good thing. And don't talk to me about the work ethic of twenty-somethings. Actually, say authors John C. Beck and Mitchell Wade, gamers will make great workers and great employees. They know how to work in teams, are creative problem solvers, and believe that nothing is impossible. But managers need to know what makes this new generation tick in order to manage them effectively. Our interview follows.
 What is important about this difference?
John C. Beck and Mitchell Wade: Games have created a real generation gap—which is more powerful because both sides tend to overlook it.
Gamers have never known a time without games, and see them as a perfectly valid tool for solving problems, relating to other human beings, and discovering one's identity. Most boomers have never seen games as anything more than a toy, and as a result, are often shocked when they see what today's games can do.
This has created massive differences in perceptions about how one looks at the world—how to approach challenges, evaluate risk, and manage other people. Both gamers and boomers will need to overcome this communication gap in order to succeed together in organizations. But as is usually the case with generational conflict, the younger one has time on its side. So boomers need to listen and learn instead of lecture and lament.
Q: For our baby boomers in the audience whose expertise with video games ended with Pac-Man, what kinds of games has this generation grown up with?
A: Games are now much more than a blob of pixels on a screen. Games tell compelling stories, explore as well as violate societal conventions, and transport players to any number of worlds—both real and imagined. They are engaging to all kinds of people, use many different mental and social skills, and are fully part of life for people under thirty-five or so. Games have allowed players to care for virtual pets and humans.  Yet games get more powerful every day.
One gaming company executive was quoted as saying, "We're going to make games that will make you cry." So we can only imagine what the future will hold.
Q: How have video games changed the way this generation views the business world?
A: Gamers approach the business world a bit more like a game. They see the different companies—and maybe the people they work with—as "players." They're way more competitive and are very passionate about "winning." They are both more optimistic and more determined about solving any kind of problem you can imagine; they think there's always going to be some combination of moves that will result in success. That drives them to be incredibly creative. They're a bit suspicious of company leaders: The game world is not big on following hierarchy. Plus, they are very confident. Like entrepreneurs, they would rather rely on their own abilities to succeed or fail. They're also more comfortable with risks, but aren't reckless.
Q: What traits mark the gamer generation that could make them especially good managers, and what traits work against them?
A: Gamers are ready to be great leaders, so they're motivated to contribute and to earn their way through whatever hurdles it takes to get to the (pretty elevated) place they believe they should be.
Gamers are also resilient. They know failure is survivable, because they have each failed literally thousands of times on the way to whatever success they have had with games. (The failure hasn't been "real," of course, but it has felt as real to them as the success has.)
They're also savvy—it's tough to pull one over on them. They may be a little overconfident in their own abilities, and they may not believe something doesn't work until they actually see it fail themselves. But with some guidance, managers should be able to marshal their best instinct, which is their love of being the hero.
Q: Today's work environment is largely about team performance. Aren't gamers loners?
A: This is one of the huge points creating the generation gap. Gaming is actually much more social than boomers understand. A lot of it is very social, done with friends, and now increasingly, over the Internet. Maybe as a result, gamers really value other people—more than people who didn't play games growing up. They also firmly believe in a team environment.
But they're not egalitarians—they believe someone should lead, they are generally happy to do it, and they have more skills than other people their age, more fluency with different leadership styles.
Q: Do male and female gamers see the world differently from each other? Would female gamers make different kinds of executives than males?
A: Historically gamers have been male, but that's changing. There are tens of millions of female gamers, and an increasing number of women are growing up gamers, participating in the same kinds of experiences.
Male gamers tend to see the world in slightly more black and white terms and like to be the star, versus female gamers who care more about the social aspects. It's also been said that males prefer games where the player has fantastical abilities in everyday settings (think superheroes) and females prefer gamers where the player has no special abilities but is in a fantastical setting (think Alice in Wonderland).
So some of the same differences you see between men and women in other settings carry through. But in some of the lessons of gaming—like taking measured risks, being the center of the action—women are learning those lessons as they play the same as men. That may change things we now take for granted.
Q: More than one boomer has bemoaned the work ethic of twenty-somethings. What does your research show about this?
A: We've heard those complaints. But what we found, to our surprise, is that gamers actually care about the companies they work for more than non-gamers. That may not always show, especially if you're using boomer standards. The secret is, gamers love a challenge and if properly motivated will rise to the occasion. They want to be respected and they want to earn that, but gaming hasn't given them a lot of appreciation for doing things "just because." So it's smart to get them excited about the goal. Make the work mean something to them.
Odds are, anyone complaining about a gamer's work ethic hasn't properly framed the task at hand to inspire them. And as one gamer pointed out to us, the boomers probably weren't getting much done in those years right after Woodstock.
Q: What's the danger for boomer managers who don't understand the gamer generation?
A: Boomer managers are leaving a LOT of value on the table, value that their competitors may not have seen yet, either. Gamers aren't just OK; they have some strengths that weren't standard in our generation. They can be almost maniacally dedicated and productive; for them, solving the problem can be a pleasant obsession like games were.
And as they come to dominate the workforce, anyone who doesn't understand them will become increasingly isolated. Imagine Ward Cleaver trying to manage in today's boomer-centric world. We're moving towards a more gamer-centered universe, both from a marketing and a management perspective. Boomers who don't understand the transition will run the risk of being left behind, unable to adapt. They'll either be trying to sell to people using completely wrong language, or they'll be trying to train using boring old methods like in classrooms and lectures. Either way, if they fail to adapt, they're going to waste a lot of the shareholders' money sticking to methods that don't work anymore.
[ Buy this book ]
by John C. Beck and Mitchell Wade
Let's begin with one of the most subconscious and therefore most powerful things that gaming teaches its natives about their place in the world: They are all customers, and the customer is always right. Or, as members of the game generation might say, "It is all about me." The world of games is deeply, implicitly commercial. Games are a consumer product, of course. But they are also a consumer experience. Like shopping, games are experiences that partake of reality and that play on powerful emotions, but that are also carefully orchestrated to give you exactly what you have paid for. The adventure is controlled through the framework of the game itself, but universally the game puts the player in direct control of the situation, from fighter pilot to jungle explorer.
Also, similar to shopping, games become far less compelling unless the game focuses all of your audiovisual inputs on the world within the screen. That trip to Abercrombie & Fitch is much less satisfying if you are consciously aware of the eye-catching displays and the simpatico clerks. In games, the moment you stop "being" a Jedi knight battling the dark side and resume "being" an ordinary guy on the family room couch, well, let's just say that you become a little less impressed with your own light saber.
 What's wrong with that? In itself, nothing. What's worth noting, though, is that many individual members of the game generation have spent thousands of hours there—hours that otherwise would have been spent in experiences that are not consumer theater. 1 What if you had spent five or ten fewer hours each week in organized sports, in unstructured play with friends, in family events that s dragged you to? And instead spent those hours in the mall, with an unlimited budget? How distorted would your view of the world, and especially your view of your place in it, be by your own current standards?
Most of us would expect a huge difference. (And, as our data set reveals, we would be correct.) In everywhere but the game world, you have more responsibility, less freedom, and a lot less help from others to feel however it is that you want to feel at that particular moment. Unlike computer-generated characters in a video game, other people have free will. If they are parents or other authority figures, they'll boss you around. Even if they are your very best friends, they'll sometimes refuse to play what you want; they'll compete when you don't want them to; they'll suggest activities that weren't on your agenda; they'll ask for your support. They might even judge you.
We're not suggesting that anyone should trade in real friends, family, and colleagues for virtual ones, though we know those thoughts sometimes do cross one's mind. But we are saying that, unless they really did grow up shopping just about all the time, with just about no constraints, boomers and their parents have probably never experienced a world quite so superficially self-affirming as the world in which gamers have largely grown up. The pleasures of interacting with live human beings are real and indispensable. But the player's role there is a far cry from "starring" in a shopping mall or digital game. It's the difference between everyone around you saying "What about me?" instead of "The customer is always right." And the game generation has grown up, in effect, hearing the latter.
Reprinted with permission of Harvard Business School Press. Got Game: How the Gamer Generation is Reshaping Business Forever by John C. Beck and Mitchell Wade. Copyright 2004 by John C. Beck and Mitchell Wade; All Rights Reserved.
Footnote:
1. By one estimate, typical America teens will have played ten thousand hours of digital games by the time they begin their careers. Marc Prensky, Digital Game-Based Learning . New York: McGraw Hill, 2001.


Welcome to my portfolio! I have always loved the surprising insights data can help us see. It can help you question your assumptions, or affirm your uncertainties. Data has the potential to tell a story better than a book, or capture a moment in time better than a photo. It is my mission to help further those possibilities. I have a particular affinity for geographic and spatial data, because I am continually interested in the intersection of people and place. Below you will find my personal Data Science projects, please reach out with any questions, comments, or recommendations. I'd love to talk about anything that is Data!
I practiced basic EDA to create a report that communicates a broad picture of a small data set. The data set was a database tracking the work of my previous business. The final product is an HTML display of the descriptive statistics of each variable contained within the data set. I used Python, Pandas, Pandas Profiling, Matplotlib, HTML, and CSS for this project.


Attempt to dig down in to the root
object and stop on the parent of the target property.
Return the progress of the mining as an array in this structure;
[root-object, base-object, base-path, target-parent, target-property]
.
dig = (root, path, force, parseFirst = yes) ->
result = [root]
if path and path.indexOf('.') isnt -1
path = path.split '.'
object = base = root[basePath = path.shift()]
object = base = tryParse object if parseFirst
while object and path.length > 1
object = object[path.shift()]
object = {} if not object? and force
result.push base, basePath, object, path.shift()
else
result.push root, path, root, path
result